[ http://jira.jboss.com/jira/browse/JBSEAM-1569?page=comments#action_12367150 ] Pete Muir commented on JBSEAM-1569: ----------------------------------- Consider using Maven pom and maven-ant task OR Ivy to manage dependencies. Advantage of using a maven pom is that this is something users are after, so we probably have to maintain one of these anyway. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-1569?page=all ] Gavin King updated JBSEAM-1569: ------------------------------- Fix Version/s: 2.0.0.GA (was: 2.0.0.CR1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-1569?page=comments#action_12369787 ] Dan Allen commented on JBSEAM-1569: ----------------------------------- I know that when the discussion of Maven2 comes up, so does the debate of relying on a remote repository to get dependencies (and unregulated transitivity). There is one very simple workaround that would keep the Seam build entirely self-contained (which I prefer). 1. Make a repo directory that mimics the structure of the Maven 2 repository with the bare minimum jar files needed for Seam (whatever they are) 2. Make a Maven 2 profile in the pom.xml with the id local-repository, setup as follows: <profiles> <profile> <id>local-repository</id> <repositories> <repository> <id>central</id> <url>file://${basedir}/repo</url> </repository> </repositories> </profile> </profiles> 3. Add a profiles.xml file adjacent to pom.xml that turns on this profile by default. <settings> <activeProfiles> <activeProfile>local-repository</activeProfile> </activeProfiles> </settings> This gives the user the flexibility to disable the self-containment if they really want to. Otherwise, all jar files would be pulled from the repo directory at the root of the project. The only really lame part about how Maven 2 deals with repositories is its implicit selection. You have to give the local repository the id "central" or else it will still try to use the central repository. There is no setting for "don't ever use the internet you stupid fool." For whatever reason, the mirrorOf element is only allowed for mirror definitions, not for repositories. Incidentally, I still think it is a good idea to publish the Seam jars to the central Maven 2 repository. That is a separate goal in my mind. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-1569?page=comments#action_12371533 ] Joris Wijlens commented on JBSEAM-1569: --------------------------------------- I used/ am using both, at first I liked Maven better but if you just want the dependency mgt feature I would go for Ivy. pro ivy specializing on dep mgt smaller and simpler to use ant is a first class citizen con ivy needs to use maven repo as public repo smaller "community" just my two cents Joris Wijlens -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-1569?page=all ] Pete Muir resolved JBSEAM-1569. ------------------------------- Resolution: Done Much improved dependency management using Maven. Compile time dependencies for Seam are done, and contribute towards improved runtime dependency information (along with Shanes chapter in the docs). We really need to be able to create dependency profiles (which Maven 2.0 doesn't have) to get proper runtime info. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-1569?page=all ] Pete Muir resolved JBSEAM-1569. ------------------------------- Fix Version/s: 2.0.0.CR2 (was: 2.0.0.GA) Resolution: Done -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira