[
http://jira.codehaus.org/browse/MNG-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214851#action_214851
]
Ondrej Zizka commented on MNG-4599:
-----------------------------------
Jason, thanks for the comment. Sorry for the tone of my previous one.
It seems that you still don't see my point. Let me put it short:
Maven is good as a build tool, but quite bad for integration testing. Perhaps
it's not intended for it, but it's natural for the QEs to try it with Maven,
because developers want to reproduce bugs and they don't want to use other tool
than for building.
Reproducing is done on released products, because whatever you may think, Maven
is not (yet) so universal to be able to build a whole product from the sources
- there are even things that can't be done that way, like signing the jars etc.
because of process matters.
So then, QA dept gets the product as a ZIP or whatever archive/package, which
contains many many .jars from various sources, not only Maven. These jars
differ for each release, including internal and candidate. Stuffing them to
Maven repo is a non-sense - they are used only once, they are used by tools
which will hardly be ever Mavenized, sometimes they need to stay in the same
directory because of security constraints, etc.
Please, please at least admit that these are valid needs, so I really have
confirmed the "Maven decision" facing to these needs.
As you suggest, I will try the user space, just - what exactly do you mean by
that? Could recommend some mailing list or forum please?
Resolved issues can't be voted. If this was changed, perhaps RFEs like this
would not get lost.
> Provide a way to create "virtual artifacts" out of plain .jar file.
> -------------------------------------------------------------------
>
> Key: MNG-4599
> URL: http://jira.codehaus.org/browse/MNG-4599
> Project: Maven 2 & 3
> Issue Type: Improvement
> Reporter: Ondrej Zizka
> Assignee: Brett Porter
>
> During the time I have been using Maven, I have come across numerous cases
> when I desperately needed to turn a simple .jar file into a dependency.
> Currently, this involves installing it properly to the repository first, and
> only then it can be used.
> I suggest to introduce some construct which would take a list of .jar files
> and turn them into dependencies in the sense they would be added to the
> classpaths, could be used for WAR overlays, etc. Of course, they would not
> have any transitional dependencies.
> <dependencyManagement>
> <jarPaths>
> <jarPath>../../releases/50GAAS/jboss-as/common/lib</jarPath>
> </jarPaths>
> ...
> </dependencyManagement>
> This would greately improve Maven's openness to non-mavenized world, and
> usability in cases when you really get a plain .jar/.war/.ear/... before
> every build cycle.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
