Issue Details (XML | Word | Printable)

Key: GALAXY-83
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: To be reviewed To be reviewed
Assignee: Dan Diephouse
Reporter: Dan Diephouse
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Galaxy

Maven repository integration

Created: 31/Jan/08 12:22 PM   Updated: 05/Feb/08 01:07 PM
Component/s: Core
Affects Version/s: 1.0-beta-1
Fix Version/s: 1.0-beta-2

Time Tracking:
Not Specified

Labels:
User impact: High


 Description  « Hide
We should be able to scan/index artifacts within a Maven repository. This requires the addition of virtual workspaces. We also need to figure out how we're going to show the data inside the workspaces.

My idea on how to do this would be to create a workspace which was actually backed by a maven repository. Then users could create another workspace which imported a set of groupId/artifactIds into it. And optionally their transitive dependencies. Maybe a Maven plugin can set this up for us. This would allow users to easily create a workspace with their application jars/artifacts in it.

I'm sure there are other ways as well. Let me know if you've got better ideas.



 All   Comments   Work Log   Change History   Transitions   FishEye      Sort Order: Ascending order - Click to sort in descending order
Dan Diephouse added a comment - 01/Feb/08 08:41 AM
I think a near term solution is to have a plugin which deploys an artifacts (and their transitive dependencies) to a workspace. in essence:

<plugin>
<configuration>
<dependencies>
... extra deps
</dependencies>
<resources>
<resource>src/main/schemas/**</resource>
</resources>
</plugin>

We're going to need this anyway to deploy artifacts which aren't published to the repository as part of a maven build anyway. We definitely need to integrate with real repositories though.


Dan Diephouse added a comment - 05/Feb/08 01:07 PM
The initial version of this is done. Going to file JIRAs for future features.