You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Alex Boisvert (JIRA)" <ji...@apache.org> on 2010/08/02 18:45:17 UTC
[jira] Created: (BUILDR-486) Buildr-generated poms should include
dependencies
Buildr-generated poms should include dependencies
-------------------------------------------------
Key: BUILDR-486
URL: https://issues.apache.org/jira/browse/BUILDR-486
Project: Buildr
Issue Type: Improvement
Components: Dependency management
Affects Versions: 1.4.1
Reporter: Alex Boisvert
Priority: Minor
Fix For: Wish List
To quote a personal email I received:
" I just realized that buildr-created poms have zero dependencies. Wtf?
That's kind of the point of publishing a pom. :-)"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-486) Buildr-generated poms should include
dependencies
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922099#action_12922099 ]
Tammo van Lessen commented on BUILDR-486:
-----------------------------------------
I started working on this, progress can be followed at http://github.com/vanto/buildr/commits/pom-deps. The current status is that artifacts now have a dependencies attribute which may contain a set of artifacts. These artifacts are then serialized to the pom (pom_xml).
Before I can continue, I'd like to discuss a couple of things:
- Should "dependency-aware artifact" mean, that we also parse POMs located in the local repo? That would be nice as it would allow something like artifact("com.example:library:jar:2.0").with_dependencies. Reading all POMs would in turn affect Buildr's performance.
- artifact.pom returns another artifact of type POM. Should artifact.pom.pom_xml == artifact.pom_xml always be true?
- I havent't found a nice way yet to set artifact.dependencies to a smart default. Should this take place in packaging/package.rb or better in java/packaging.rb, similar to the :libs handling?
Would be great to get some hints (hint, hint ;))
> Buildr-generated poms should include dependencies
> -------------------------------------------------
>
> Key: BUILDR-486
> URL: https://issues.apache.org/jira/browse/BUILDR-486
> Project: Buildr
> Issue Type: Improvement
> Components: Dependency management
> Affects Versions: 1.4.1
> Reporter: Alex Boisvert
> Priority: Minor
> Fix For: Wish List
>
>
> To quote a personal email I received:
> " I just realized that buildr-created poms have zero dependencies. Wtf?
> That's kind of the point of publishing a pom. :-)"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-486) Buildr-generated poms should include
dependencies
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894595#action_12894595 ]
Alex Boisvert commented on BUILDR-486:
--------------------------------------
Was also brought up in this thread earlier:
http://markmail.org/thread/6yda7wngx6zpad5a
> Buildr-generated poms should include dependencies
> -------------------------------------------------
>
> Key: BUILDR-486
> URL: https://issues.apache.org/jira/browse/BUILDR-486
> Project: Buildr
> Issue Type: Improvement
> Components: Dependency management
> Affects Versions: 1.4.1
> Reporter: Alex Boisvert
> Priority: Minor
> Fix For: Wish List
>
>
> To quote a personal email I received:
> " I just realized that buildr-created poms have zero dependencies. Wtf?
> That's kind of the point of publishing a pom. :-)"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-486) Buildr-generated poms should include
dependencies
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922843#action_12922843 ]
Alex Boisvert commented on BUILDR-486:
--------------------------------------
1) calculating transitive dependencies should be optional. currently we use transitive(artifact_spec). i'm not opposed to adding artifact(spec).dependencies.
2) i don't think we should try to keep artifact.pom.pom_xml and artifact.pom_xml the same at all times. they are fundamentally different. artifact.pom returns another artifact, which may already exist on the file system. artifact.pom_xml provides the xml content for the creation of a pom.
3) i'd probably go with java/packaging.rb similar to how manifest are handled (e.g. WithManifest).
> Buildr-generated poms should include dependencies
> -------------------------------------------------
>
> Key: BUILDR-486
> URL: https://issues.apache.org/jira/browse/BUILDR-486
> Project: Buildr
> Issue Type: Improvement
> Components: Dependency management
> Affects Versions: 1.4.1
> Reporter: Alex Boisvert
> Priority: Minor
> Fix For: Wish List
>
>
> To quote a personal email I received:
> " I just realized that buildr-created poms have zero dependencies. Wtf?
> That's kind of the point of publishing a pom. :-)"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.