[jira] Created: (SUREFIRE-783) A boolean option to push all maven props to system props
A boolean option to push all maven props to system props Key: SUREFIRE-783 URL: https://jira.codehaus.org/browse/SUREFIRE-783 Project: Maven Surefire Issue Type: Improvement Components: process forking Affects Versions: 2.10 Reporter: Benson Margulies I'd like to implement an idea, but only if the serious sure-fire-ists agree. At my shop, people constantly expect that setting a Maven property will produce a -D for them in tests, and they have to be taught, over and over, the contrary. Parallel to a feature of antrun, I propose to make an option to make it trivial to make surefire match such expectations. If this option is true, all the maven properties from the pom, plus the same list of 'common' global props from antrun, would be turned into system property values. I'm a committer I'll take care of this if there are no objections. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MWAR-240) archiveClasses and attachClasses in 2.1
[
https://jira.codehaus.org/browse/MWAR-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282418#comment-282418
]
Liya Katz commented on MWAR-240:
same problem with maven 3.0.3 and war-plugin 2.1.1
had to downgrade to 2.1-beta-1
> archiveClasses and attachClasses in 2.1
> ---
>
> Key: MWAR-240
> URL: https://jira.codehaus.org/browse/MWAR-240
> Project: Maven 2.x WAR Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> Java version: 1.6.0_18
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"
>Reporter: Sergiy Shyrkov
> Attachments: effective-pom.out, mwar-240-test-case.zip
>
>
> There seems to be a regression between 2.1-beta-1 and 2.1 with regard to
> archiveClasses and attachClasses options.
> My use case:
> I have a WAR project with Java classes and I am setting both archiveClasses
> and attachClasses to true.
> With 2.1-beta-1 it was working correctly (mvn clean install) --> I got
> classes packaged into a JAR and placed into WEB-INF/lib and I got that JAR
> artifact deployed to my Maven repository.
> Just upgraded to 2.1 and I got the following with the same use case: I got
> classes packaged into a JAR and placed into WEB-INF/lib (correct) and I got
> an empty JAR artifact (only META-INF/ present) deployed to my Maven
> repository (incorrect).
> Looking at the code in 2.1 of WarMojo (line 230) I am seeing that the classes
> folder (for classes to be included into attached artifact) is empty, because
> it was cleared before due to archiveClasses=true
> Trying to debug both code branches I am seeing a difference between
> 2.1-beta-1 and 2.1 in that the
> getJarArchiver().getDirs() before the call to packager.packageClasses()
> method (line 233/234)
> is empty in the 2.1:
>(java.util.HashMap) {}
> whereas it is not in 2.1-beta-1. It contains a list of all my classes,
> perhaps because the same archiver instance was used to package them into JAR
> for WEB-INF/lib.
> That is why I am getting all my classes in the attached artifact with
> 2.1-beta-1
> I would really need your help in understanding the "correct" behaviour.
> Is this a regression bug for 2.1 or I am completely wrong in my expectations
> about archiveClasses and attachClasses used together?
> Kind regards
> Sergiy Shyrkov
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MWAR-256) it's not possible to create classes attachment without classifier
[
https://jira.codehaus.org/browse/MWAR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282419#comment-282419
]
Liya Katz commented on MWAR-256:
It's quite odd that the jar inside the war does not have any classifier, but if
the same jar is chosen to be attached as an artifact to the project, it has to
have a classifier. There must be some disabling option for this annoying
"feature".
> it's not possible to create classes attachment without classifier
> -
>
> Key: MWAR-256
> URL: https://jira.codehaus.org/browse/MWAR-256
> Project: Maven 2.x WAR Plugin
> Issue Type: Bug
>Affects Versions: 2.1.1
>Reporter: Rafal Krzewski
>
> I would like to package classes in my war-packaged project into a jar, but I
> don't want to use default 'classes' classifier assigned by the plugin. The
> generated artifacts have distinct packaging types, so there is no conflict
> and the classifier provides no useful additional information. Using the
> following configuration:
> {quote}
> {{}}
> {{}}
> {{}}
> {quote}
> Results in "classes" classifier being used anyway. If I understand the
> behavior correctly Plexus assigns the variable it's default value, when
> presented an empty input. I don't think this can be fixed in way that is both
> clean and backward compatible. Either the default value will change, which
> would break existing builds that don't specify plugin version explicitly, or
> some clunky additional parameter like
> {{false}}, or magic value like
> {{NONE}} need to be introduced.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MAVENUPLOAD-2306) Mysema Source sync
[ https://jira.codehaus.org/browse/MAVENUPLOAD-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timo Westkämper reopened MAVENUPLOAD-2306: -- We have moved the contents of the source.mysema.com server to a new machine with a new IP and after that nothing has been moved. Rsync should be working fine. Could you check what went wrong? > Mysema Source sync > -- > > Key: MAVENUPLOAD-2306 > URL: https://jira.codehaus.org/browse/MAVENUPLOAD-2306 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Timo Westkämper >Assignee: Carlos Sanchez > > Please sync the following : > "com.mysema.home","rsync://source.mysema.com/releases","rsync","Timo > Westkämper","i...@mysema.com",, > "com.mysema.l10n","rsync://source.mysema.com/releases","rsync","Timo > Westkämper","i...@mysema.com",, > "com.mysema.querydsl","rsync://source.mysema.com/releases","rsync","Timo > Westkämper","i...@mysema.com",, > "com.mysema.web","rsync://source.mysema.com/releases","rsync","Timo > Westkämper","i...@mysema.com",, -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
