[jira] Updated: (MNG-2284) Cannot specify additional classpath entries in manifest when using addClasspath
[ http://jira.codehaus.org/browse/MNG-2284?page=all ] Fredrik Vraalsen updated MNG-2284: -- Attachment: MNG-2284-addClasspath-and-user-specified-classpath.patch > Cannot specify additional classpath entries in manifest when using > addClasspath > --- > > Key: MNG-2284 > URL: http://jira.codehaus.org/browse/MNG-2284 > Project: Maven 2 > Type: Bug > Components: maven-archiver > Versions: 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4 > Environment: Maven 2.0.4, maven-jar-plugin 2.0 and 2.1-SNAPSHOT, JDK > 1.5.0_06, Windows XP > Reporter: Fredrik Vraalsen > Assignee: Mike Perham > Fix For: 2.0.5 > Attachments: MNG-2284-addClasspath-and-user-specified-classpath.patch, > MNG-archiver-classpath.patch, pom.xml > > > When using addClasspath, e.g. in the maven-jar-plugin, it is not possible to > add additional classpath entries using manifestEntries, as this generates an > illegal manifest file (contains two Class-Path entries). Please see > http://jira.codehaus.org/browse/MJAR-41 > I have been looking through the code, and it seems this might need to be > resolved in MavenArchiver? I've attached a simple fix that solves the > problem for me, but a more thorough solution might be needed of course. ;-) -- 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
[jira] Created: (MNGECLIPSE-155) m2 plugin not reading ~/.m2/settings.xml
m2 plugin not reading ~/.m2/settings.xml -- Key: MNGECLIPSE-155 URL: http://jira.codehaus.org/browse/MNGECLIPSE-155 Project: Maven 2.x Extension for Eclipse Type: Bug Components: Maven Launcher Versions: 0.0.9 Environment: Eclipse 3.2 Reporter: Ben Fortuna Assigned to: Eugene Kuleshov I have SSH deployment specified in the POM node, and specify user credentials (username, password) in ~/.m2/settings.xml. When I try to execute goal "deploy" the user credentials in settings.xml are ignored. Note that the deploy goal works fine from command line. regards, ben -- 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
[jira] Updated: (MNG-2284) Cannot specify additional classpath entries in manifest when using addClasspath
[ http://jira.codehaus.org/browse/MNG-2284?page=all ] Fredrik Vraalsen updated MNG-2284: -- Attachment: MNG-2284-fix-addClasspath-and-user-specified-classpath-2.patch > Cannot specify additional classpath entries in manifest when using > addClasspath > --- > > Key: MNG-2284 > URL: http://jira.codehaus.org/browse/MNG-2284 > Project: Maven 2 > Type: Bug > Components: maven-archiver > Versions: 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4 > Environment: Maven 2.0.4, maven-jar-plugin 2.0 and 2.1-SNAPSHOT, JDK > 1.5.0_06, Windows XP > Reporter: Fredrik Vraalsen > Assignee: Mike Perham > Fix For: 2.0.5 > Attachments: MNG-2284-addClasspath-and-user-specified-classpath.patch, > MNG-2284-fix-addClasspath-and-user-specified-classpath-2.patch, > MNG-archiver-classpath.patch, pom.xml > > > When using addClasspath, e.g. in the maven-jar-plugin, it is not possible to > add additional classpath entries using manifestEntries, as this generates an > illegal manifest file (contains two Class-Path entries). Please see > http://jira.codehaus.org/browse/MJAR-41 > I have been looking through the code, and it seems this might need to be > resolved in MavenArchiver? I've attached a simple fix that solves the > problem for me, but a more thorough solution might be needed of course. ;-) -- 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
[jira] Updated: (MNG-2284) Cannot specify additional classpath entries in manifest when using addClasspath
[ http://jira.codehaus.org/browse/MNG-2284?page=all ] Kenney Westerhof updated MNG-2284: -- Attachment: (was: MNG-archiver-classpath.patch) > Cannot specify additional classpath entries in manifest when using > addClasspath > --- > > Key: MNG-2284 > URL: http://jira.codehaus.org/browse/MNG-2284 > Project: Maven 2 > Type: Bug > Components: maven-archiver > Versions: 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4 > Environment: Maven 2.0.4, maven-jar-plugin 2.0 and 2.1-SNAPSHOT, JDK > 1.5.0_06, Windows XP > Reporter: Fredrik Vraalsen > Assignee: Kenney Westerhof > Fix For: 2.0.5 > Attachments: MNG-2284-fix-addClasspath-and-user-specified-classpath-2.patch, > pom.xml > > > When using addClasspath, e.g. in the maven-jar-plugin, it is not possible to > add additional classpath entries using manifestEntries, as this generates an > illegal manifest file (contains two Class-Path entries). Please see > http://jira.codehaus.org/browse/MJAR-41 > I have been looking through the code, and it seems this might need to be > resolved in MavenArchiver? I've attached a simple fix that solves the > problem for me, but a more thorough solution might be needed of course. ;-) -- 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
[jira] Updated: (MNG-2284) Cannot specify additional classpath entries in manifest when using addClasspath
[ http://jira.codehaus.org/browse/MNG-2284?page=all ] Kenney Westerhof updated MNG-2284: -- Attachment: (was: MNG-2284-addClasspath-and-user-specified-classpath.patch) > Cannot specify additional classpath entries in manifest when using > addClasspath > --- > > Key: MNG-2284 > URL: http://jira.codehaus.org/browse/MNG-2284 > Project: Maven 2 > Type: Bug > Components: maven-archiver > Versions: 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4 > Environment: Maven 2.0.4, maven-jar-plugin 2.0 and 2.1-SNAPSHOT, JDK > 1.5.0_06, Windows XP > Reporter: Fredrik Vraalsen > Assignee: Kenney Westerhof > Fix For: 2.0.5 > Attachments: MNG-2284-fix-addClasspath-and-user-specified-classpath-2.patch, > pom.xml > > > When using addClasspath, e.g. in the maven-jar-plugin, it is not possible to > add additional classpath entries using manifestEntries, as this generates an > illegal manifest file (contains two Class-Path entries). Please see > http://jira.codehaus.org/browse/MJAR-41 > I have been looking through the code, and it seems this might need to be > resolved in MavenArchiver? I've attached a simple fix that solves the > problem for me, but a more thorough solution might be needed of course. ;-) -- 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
[jira] Closed: (MNGECLIPSE-155) m2 plugin not reading ~/.m2/settings.xml
[ http://jira.codehaus.org/browse/MNGECLIPSE-155?page=all ] Eugene Kuleshov closed MNGECLIPSE-155: -- Resolution: Duplicate Version in a trunk should resolve this > m2 plugin not reading ~/.m2/settings.xml > -- > > Key: MNGECLIPSE-155 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-155 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Components: Maven Launcher > Versions: 0.0.9 > Environment: Eclipse 3.2 > Reporter: Ben Fortuna > Assignee: Eugene Kuleshov > > > I have SSH deployment specified in the POM node, and > specify user credentials (username, password) in ~/.m2/settings.xml. > When I try to execute goal "deploy" the user credentials in settings.xml are > ignored. > Note that the deploy goal works fine from command line. > regards, > ben -- 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
[jira] Closed: (MEV-406) XMLBeans pom is missing dependency
[ http://jira.codehaus.org/browse/MEV-406?page=all ] Carlos Sanchez closed MEV-406: -- Assign To: Carlos Sanchez Resolution: Fixed Added 2.0.0-1 wth pached pom > XMLBeans pom is missing dependency > -- > > Key: MEV-406 > URL: http://jira.codehaus.org/browse/MEV-406 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: David Jencks > Assignee: Carlos Sanchez > Attachments: xbean-2.0.0.pom > > > The xmlbeans 2.0.0 pom is missing the one required dependency on the stax > api. xmlbeans seems to ship a jsr-173-api jar that is of AFAICT unknown > provenance. AFAIK everyone has been using the stax-api jar with no problems > for years: certainly geronimo has. > To see that this is the single required dependency, consult > http://xmlbeans.apache.org/documentation/conInstallGuide.html and look at the > bottom of the page at the suggested classpath setup, e.g.: > export > CLASSPATH=$XMLBEANS_HOME/lib/xbean.jar:$XMLBEANS_HOME/lib/jsr173_1.0_api.jar:$CLASSPATH > Here's the pom, the instructions at > http://maven.apache.org/guides/mini/guide-maven-evangelism.html point to > invalid svn locations so I cannot check out the original and supply a patch. > The pom goes at ~/.m2/repository/xmlbeans/xbean/2.0.0/xbean-2.0.0.pom in a > local repo. I'll attach it as well. > > 4.0.0 > xmlbeans > xbean > 2.0.0 > > > stax > stax-api > 1.0 > > > -- 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
[jira] Closed: (MAVENUPLOAD-980) Upload JUG (Java UUID Generator) 2.0.0 (LGPL)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-980?page=all ] Carlos Sanchez closed MAVENUPLOAD-980: -- Assign To: Carlos Sanchez Resolution: Fixed uploaded to org.safehaus.jug group You must use to choose the different licenses > Upload JUG (Java UUID Generator) 2.0.0 (LGPL) > - > > Key: MAVENUPLOAD-980 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-980 > Project: maven-upload-requests > Type: Task > Reporter: Matt Whitlock > Assignee: Carlos Sanchez > Attachments: jug-lgpl-2.0.0-bundle.jar > > > http://home.mattwhitlock.com:8080/~mattw/jug-lgpl-2.0.0-bundle.jar > http://jug.safehaus.org/ > JUG is a pure java UUID generator, that can be used either as a component in > a bigger application, or as a standalone command line tool (a la 'uuidgen'). > UUIDs are 128-bit Universally Unique IDentifiers (aka GUID, Globally Unique > IDentifier used in Windows world). [see project site for more] -- 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
[jira] Closed: (MAVENUPLOAD-979) Please upload jgraph 5.8.3.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-979?page=all ] Carlos Sanchez closed MAVENUPLOAD-979: -- Assign To: Carlos Sanchez Resolution: Fixed > Please upload jgraph 5.8.3.1 > > > Key: MAVENUPLOAD-979 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-979 > Project: maven-upload-requests > Type: Task > Reporter: Fredrik Vraalsen > Assignee: Carlos Sanchez > > > http://www.jgraph.com/ > http://sourceforge.net/projects/jgraph/ > JGraph is a Graph Visualization and Layout library licensed under the LGPL. > The newest version found on ibiblio is v.5.5.1 which was released in May > 2005. The latest release on Sourceforge is 5.8.3.1 (June 21st 2006): > http://sourceforge.net/project/shownotes.php?release_id=426575&group_id=43118 -- 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
[jira] Commented: (MAVENUPLOAD-978) Upload ejb-3.0-public-draft-20060502 (needed for hibernate)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-978?page=comments#action_69309 ] Carlos Sanchez commented on MAVENUPLOAD-978: what is the license? > Upload ejb-3.0-public-draft-20060502 (needed for hibernate) > --- > > Key: MAVENUPLOAD-978 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-978 > Project: maven-upload-requests > Type: Task > Reporter: Andrea Aime > > > http://www.webalice.it/andrea.aime/ejb-3.0-public-draft-20060502-bundle.jar > http://www.hibernate.org > The hibernate annotations 3.2cr1 needs this dependency, but it's not > published onto ibiblio, so build is not possible. -- 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
[jira] Closed: (MAVENUPLOAD-967) JSON library from json.org
[ http://jira.codehaus.org/browse/MAVENUPLOAD-967?page=all ] Carlos Sanchez closed MAVENUPLOAD-967: -- Assign To: Carlos Sanchez Resolution: Incomplete > JSON library from json.org > -- > > Key: MAVENUPLOAD-967 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-967 > Project: maven-upload-requests > Type: Task > Reporter: Andres Almiray > Assignee: Carlos Sanchez > Attachments: json-1.0.tar.gz > > > This bundle includes the json library posted by Douglas Crockford > (http://www.json.org/java/) plus some additions I (Andres Almiray) > made to JSONObject and JSONArray to support nested beans and object graphs. > This is a very lightweight library (43K) to parse objects to JSON and back > again. > I'm attaching the binary dist (including docs) created by maven. -- 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
[jira] Closed: (MAVENUPLOAD-977) please uplaod Jamon 2.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-977?page=all ] Carlos Sanchez closed MAVENUPLOAD-977: -- Assign To: Carlos Sanchez Resolution: Fixed > please uplaod Jamon 2.0 > --- > > Key: MAVENUPLOAD-977 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-977 > Project: maven-upload-requests > Type: Task > Reporter: nicolas de loof > Assignee: Carlos Sanchez > > > Jamon is a Java API that allows developers to easily monitor production > applications -- 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
[jira] Closed: (MAVENUPLOAD-965) Upload retroweaver-all 1.2.3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-965?page=all ] Carlos Sanchez closed MAVENUPLOAD-965: -- Assign To: Carlos Sanchez Resolution: Incomplete > Upload retroweaver-all 1.2.3 > > > Key: MAVENUPLOAD-965 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-965 > Project: maven-upload-requests > Type: Task > Reporter: Jochen Wiedmann > Assignee: Carlos Sanchez > > > RetroWeaver transforms Java classes, which have been compiled by a Java 5 > compiler, into class files, that are accepable by Java 1.4. Ibiblio already > contains version 1.0 (under the group net.sourceforge.retroweaver). > I am not the author, but would like to use this version in plugins. -- 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
[jira] Closed: (MAVENUPLOAD-975) Upload new AspectJ 1.5.2 artifacts to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-975?page=all ] Carlos Sanchez closed MAVENUPLOAD-975: -- Assign To: Carlos Sanchez Resolution: Fixed > Upload new AspectJ 1.5.2 artifacts to ibiblio > - > > Key: MAVENUPLOAD-975 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-975 > Project: maven-upload-requests > Type: Task > Reporter: Kaare Nilsen > Assignee: Carlos Sanchez > Attachments: aspectjlib-1.5.2-bundle.jar > > > the aspectjlib artifact -- 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
[jira] Closed: (MAVENUPLOAD-974) Upload new AspectJ 1.5.2 artifacts to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-974?page=all ] Carlos Sanchez closed MAVENUPLOAD-974: -- Assign To: Carlos Sanchez Resolution: Fixed > Upload new AspectJ 1.5.2 artifacts to ibiblio > - > > Key: MAVENUPLOAD-974 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-974 > Project: maven-upload-requests > Type: Task > Reporter: Kaare Nilsen > Assignee: Carlos Sanchez > Attachments: aspectjrt-1.5.2-bundle.jar, aspectjtools-1.5.2.jar-bundle.jar, > aspectjtools-1.5.2.pom, aspectjweaver-1.5.2-bundle.jar > > > There will be one more with the aspectjlib (could not fit into this issue) -- 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
[jira] Updated: (MAVENUPLOAD-978) Upload ejb-3.0-public-draft-20060502 (needed for hibernate)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-978?page=all ] Andrea Aime updated MAVENUPLOAD-978: Attachment: license.txt > Upload ejb-3.0-public-draft-20060502 (needed for hibernate) > --- > > Key: MAVENUPLOAD-978 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-978 > Project: maven-upload-requests > Type: Task > Reporter: Andrea Aime > Attachments: license.txt > > > http://www.webalice.it/andrea.aime/ejb-3.0-public-draft-20060502-bundle.jar > http://www.hibernate.org > The hibernate annotations 3.2cr1 needs this dependency, but it's not > published onto ibiblio, so build is not possible. -- 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
[jira] Created: (CONTINUUM-762) GMAIL notifier don't work
GMAIL notifier don't work
-
Key: CONTINUUM-762
URL: http://jira.codehaus.org/browse/CONTINUUM-762
Project: Continuum
Type: Bug
Components: Mail Notifier
Versions: 1.0.3
Environment: windows XP
Reporter: Eric Reboisson
The GMAIL configuration for outgoing mail is :
# Sélectionnez " Server Settings " (Paramètres du serveur) sous le nouveau
compte.
# Activez la case à cocher " Use secure connection (SSL) " (Utiliser une
connexion sécurisée (SSL)) et vérifiez que " 995 " apparaît dans le champ "
Port ".
# Sélectionnez " Outgoing Server (SMTP) " (Serveur sortant (SMTP)) sous le
nouveau compte.
# Entrez " smtp.gmail.com " dans le champ " Server Name " (Nom du serveur) sous
" Outgoing Server (SMTP) Settings " (Paramètres du serveur sortant (SMTP)) et
entrez " 587 " dans le champ " Port ".
# Activez la case à cocher " Use name and password " (Utiliser un nom et un mot
de passe) et entrez votre nom d'utilisateur Gmail (" @gmail.com " compris) dans
le champ " User Name " (Nom de l'utilisateur).
# Sélectionnez " TLS " sous " Use secure connection " (Utiliser une connexion
sécurisée) et cliquez sur " OK ".
# Vérifiez que les informations figurant sous " Congratulations! "
(Félicitation !) sont correctes et cliquez sur " Finish " (Terminer).
I tried to put this values in the application.xml file in
continuum-1.0.3\apps\continuum\conf but the notification don't work.
Maybe the TLS system of GMAIL prevents the working of CONTINUUM
Best regards
--
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
[jira] Created: (MSUREFIRE-145) Plugin not longer sets system properties when forking is on and debugging information is not correct
Plugin not longer sets system properties when forking is on and debugging
information is not correct
Key: MSUREFIRE-145
URL: http://jira.codehaus.org/browse/MSUREFIRE-145
Project: Maven 2.x Surefire Plugin
Type: Bug
Versions: 2.3
Reporter: Vincent Massol
Priority: Blocker
The following code is in SurefirePlugin.java:
{code:java}
processSystemProperties( !fork.isForking() );
if ( getLog().isDebugEnabled() )
{
showMap( systemProperties, "system property" );
}
{code}
2 problems:
1) fork.isForking() is false when forking is enabled and thus system properties
are not set:
{code:java}
protected void processSystemProperties( boolean setInSystem )
{
[...]
if ( setInSystem )
{
// Add all system properties configured by the user
Iterator iter = systemProperties.keySet().iterator();
while ( iter.hasNext() )
{
String key = (String) iter.next();
String value = systemProperties.getProperty( key );
System.setProperty( key, value );
}
}
}
{code}
2) showMap() is called regardless of whether the system properties are set or
not, leading to the following kind of misleading logs:
{noformat}
[...]
[DEBUG] Setting system property [cargo.jetty4x.port]=[8280]
[DEBUG] Setting system property [cargo.jetty6x.port]=[8280]
[DEBUG] Setting system property [cargo.jetty5x.port]=[8280]
[...]
{noformat}
Those properties are actually NOT set.
--
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
[jira] Commented: (MSUREFIRE-145) Plugin not longer sets system properties when forking is on and debugging information is not correct
[ http://jira.codehaus.org/browse/MSUREFIRE-145?page=comments#action_69313
]
Vincent Massol commented on MSUREFIRE-145:
--
Note: The surefire plugin started failing after version 2.1.3 (this is the last
working version for me).
> Plugin not longer sets system properties when forking is on and debugging
> information is not correct
>
>
> Key: MSUREFIRE-145
> URL: http://jira.codehaus.org/browse/MSUREFIRE-145
> Project: Maven 2.x Surefire Plugin
> Type: Bug
> Versions: 2.3
> Reporter: Vincent Massol
> Priority: Blocker
>
>
> The following code is in SurefirePlugin.java:
> {code:java}
> processSystemProperties( !fork.isForking() );
> if ( getLog().isDebugEnabled() )
> {
> showMap( systemProperties, "system property" );
> }
> {code}
> 2 problems:
> 1) fork.isForking() is false when forking is enabled and thus system
> properties are not set:
> {code:java}
> protected void processSystemProperties( boolean setInSystem )
> {
> [...]
> if ( setInSystem )
> {
> // Add all system properties configured by the user
> Iterator iter = systemProperties.keySet().iterator();
> while ( iter.hasNext() )
> {
> String key = (String) iter.next();
> String value = systemProperties.getProperty( key );
> System.setProperty( key, value );
> }
> }
> }
> {code}
> 2) showMap() is called regardless of whether the system properties are set
> or not, leading to the following kind of misleading logs:
> {noformat}
> [...]
> [DEBUG] Setting system property [cargo.jetty4x.port]=[8280]
> [DEBUG] Setting system property [cargo.jetty6x.port]=[8280]
> [DEBUG] Setting system property [cargo.jetty5x.port]=[8280]
> [...]
> {noformat}
> Those properties are actually NOT set.
--
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
[jira] Closed: (MINSTALL-26) Add classifier parameter to install-file goal
[ http://jira.codehaus.org/browse/MINSTALL-26?page=all ] Mike Perham closed MINSTALL-26: --- Assign To: Mike Perham Resolution: Duplicate MINSTALL-24 > Add classifier parameter to install-file goal > - > > Key: MINSTALL-26 > URL: http://jira.codehaus.org/browse/MINSTALL-26 > Project: Maven 2.x Install Plugin > Type: Improvement > Reporter: Allan Ramirez > Assignee: Mike Perham > > > It would be nice if the install-file goal could also install an artifact with > classifier as deploy-file does. -- 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
[jira] Commented: (MINSTALL-27) Review Plugin Documentation
[ http://jira.codehaus.org/browse/MINSTALL-27?page=comments#action_69316 ] Mike Perham commented on MINSTALL-27: - Allan, I revised your documentation a bit to clean up the English and added a site.xml. > Review Plugin Documentation > --- > > Key: MINSTALL-27 > URL: http://jira.codehaus.org/browse/MINSTALL-27 > Project: Maven 2.x Install Plugin > Type: Task > Reporter: Allan Ramirez > Assignee: Allan Ramirez > > Original Estimate: 10 hours >Time Spent: 12 hours > Remaining: 0 minutes > -- 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
[jira] Closed: (MINSTALL-24) Unable to install source or javadoc artifacts in local repository
[ http://jira.codehaus.org/browse/MINSTALL-24?page=all ] Mike Perham closed MINSTALL-24: --- Resolution: Fixed Fix Version: 2.2 Fixed and added unit test. > Unable to install source or javadoc artifacts in local repository > - > > Key: MINSTALL-24 > URL: http://jira.codehaus.org/browse/MINSTALL-24 > Project: Maven 2.x Install Plugin > Type: Bug > Versions: 2.1 > Reporter: Chris Hagmann > Assignee: Mike Perham > Priority: Critical > Fix For: 2.2 > > > I couldn't find a way of installing a source archive or a javadoc archive in > the local repository. Basically I'm missing the option to specify a > classifier when invoking mvn install:install-file. As you can see in the > output below it overwrites the main artifact (e.g. xmlc-base-2.2.9.jar) > F:\downloads\xmlc-src-2.2.9\xmlc-src-2.2.9\xmlc\modules\xmlc\src>mvn > install:ins > tall-file -Dfile=xmlc-base-2.2.9-sources.jar -DgroupId=org.enhydra.xmlc > -Dartifa > ctId=xmlc-base -Dversion=2.2.9 -Dclassifier=sources -Dpackaging=jar > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'install'. > [INFO] > - > --- > [INFO] Building Maven Default Project > [INFO]task-segment: [install:install-file] (aggregator-style) > [INFO] > - > --- > [INFO] [install:install-file] > [INFO] Installing > F:\downloads\xmlc-src-2.2.9\xmlc-src-2.2.9\xmlc\modules\xmlc\s > rc\xmlc-base-2.2.9-sources.jar to > C:\tools\maven\m2-repository\org\enhydra\xmlc\ > xmlc-base\2.2.9\xmlc-base-2.2.9.jar > [INFO] > - > --- > [INFO] BUILD SUCCESSFUL > [INFO] > - > --- > [INFO] Total time: 1 second > [INFO] Finished at: Tue Jun 13 12:58:16 PDT 2006 > [INFO] Final Memory: 2M/4M > [INFO] > - > --- > The exact same works when using the deploy plugin to install a source > artifact in the remote repository, because that plugin accepts an optional > classifier. -- 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
[jira] Closed: (MINSTALL-23) Issue tracking URL points to maven 2 jira.
[ http://jira.codehaus.org/browse/MINSTALL-23?page=all ] Mike Perham closed MINSTALL-23: --- Resolution: Fixed Fix Version: 2.2 > Issue tracking URL points to maven 2 jira. > -- > > Key: MINSTALL-23 > URL: http://jira.codehaus.org/browse/MINSTALL-23 > Project: Maven 2.x Install Plugin > Type: Bug > Reporter: Shinobu Kawai > Assignee: Mike Perham > Priority: Trivial > Fix For: 2.2 > > > http://maven.apache.org/plugins/maven-install-plugin/issue-tracking.html > The issue tracking URL should be http://jira.codehaus.org/browse/MINSTALL -- 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
[jira] Created: (MWAR-61) Document how to set manifest classpath and exclude dependency from WEB-INF/lib
Document how to set manifest classpath and exclude dependency from WEB-INF/lib -- Key: MWAR-61 URL: http://jira.codehaus.org/browse/MWAR-61 Project: Maven 2.x War Plugin Type: Improvement Versions: 2.0.1 Reporter: David Jencks Attachments: war-plugin-manifestcp-doc.patch I had to get some help from evenisse to figure out how to generate the manifest classpath yet not include all the dependencies in WEB-INF/lib. I still don't know how to get a dependency into WEB-INF/lib but not the manifest classpath when generating the manifest classpath, but this should help anyone just trying to use a manifest cp in an ear. -- 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
[jira] Created: (MEV-422) Fix the sha1 and md5 checksums for all maven-metadata.xml in repository
Fix the sha1 and md5 checksums for all maven-metadata.xml in repository --- Key: MEV-422 URL: http://jira.codehaus.org/browse/MEV-422 Project: Maven Evangelism Type: Task Reporter: Matt Whitlock Every maven-metadata.xml.md5 and maven-metadata.xml.sha1 I've looked at in the repository is invalid. All of the maven-metadata.xml.md5 contain "d41d8cd98f00b204e9800998ecf8427e", which is the MD5 hash of the empty string. All of the maven-metadata.xml.sha1 contain "da39a3ee5e6b4b0d3255bfef95601890afd80709", which is the SHA1 hash of the empty string. Some script somewhere is not generating these files correctly. Please fix the script that is responsible for generating these checksum files for the maven-metadata.xml files, and recursively regenerate the checksums for the maven-metadata.xml files in the repository. -- 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
[jira] Commented: (MEV-422) Fix the sha1 and md5 checksums for all maven-metadata.xml in repository
[ http://jira.codehaus.org/browse/MEV-422?page=comments#action_69328 ]
Matt Whitlock commented on MEV-422:
---
Actually, it looks like only the maven-metadata.xml.{md5,sha1} older than a
certain date are incorrect. The more recently modified ones appear to be okay.
So the source of the problem has likely been fixed, but there are an awful lot
of checksums in the repository that need to be fixed.
> Fix the sha1 and md5 checksums for all maven-metadata.xml in repository
> ---
>
> Key: MEV-422
> URL: http://jira.codehaus.org/browse/MEV-422
> Project: Maven Evangelism
> Type: Task
> Reporter: Matt Whitlock
>
>
> Every maven-metadata.xml.md5 and maven-metadata.xml.sha1 I've looked at in
> the repository is invalid. All of the maven-metadata.xml.md5 contain
> "d41d8cd98f00b204e9800998ecf8427e", which is the MD5 hash of the empty
> string. All of the maven-metadata.xml.sha1 contain
> "da39a3ee5e6b4b0d3255bfef95601890afd80709", which is the SHA1 hash of the
> empty string. Some script somewhere is not generating these files correctly.
> Please fix the script that is responsible for generating these checksum files
> for the maven-metadata.xml files, and recursively regenerate the checksums
> for the maven-metadata.xml files in the repository.
--
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
[jira] Commented: (MSUREFIRE-145) Plugin not longer sets system properties when forking is on and debugging information is not correct
[ http://jira.codehaus.org/browse/MSUREFIRE-145?page=comments#action_69331
]
Brett Porter commented on MSUREFIRE-145:
btw, I think an appropriate affects version is the ones you tested (2.2). You
can't say it will affect 2.3 since that's not released yet.
> Plugin not longer sets system properties when forking is on and debugging
> information is not correct
>
>
> Key: MSUREFIRE-145
> URL: http://jira.codehaus.org/browse/MSUREFIRE-145
> Project: Maven 2.x Surefire Plugin
> Type: Bug
> Versions: 2.3
> Reporter: Vincent Massol
> Priority: Blocker
>
>
> The following code is in SurefirePlugin.java:
> {code:java}
> processSystemProperties( !fork.isForking() );
> if ( getLog().isDebugEnabled() )
> {
> showMap( systemProperties, "system property" );
> }
> {code}
> 2 problems:
> 1) fork.isForking() is false when forking is enabled and thus system
> properties are not set:
> {code:java}
> protected void processSystemProperties( boolean setInSystem )
> {
> [...]
> if ( setInSystem )
> {
> // Add all system properties configured by the user
> Iterator iter = systemProperties.keySet().iterator();
> while ( iter.hasNext() )
> {
> String key = (String) iter.next();
> String value = systemProperties.getProperty( key );
> System.setProperty( key, value );
> }
> }
> }
> {code}
> 2) showMap() is called regardless of whether the system properties are set
> or not, leading to the following kind of misleading logs:
> {noformat}
> [...]
> [DEBUG] Setting system property [cargo.jetty4x.port]=[8280]
> [DEBUG] Setting system property [cargo.jetty6x.port]=[8280]
> [DEBUG] Setting system property [cargo.jetty5x.port]=[8280]
> [...]
> {noformat}
> Those properties are actually NOT set.
--
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
[jira] Commented: (MSUREFIRE-145) Plugin not longer sets system properties when forking is on and debugging information is not correct
[ http://jira.codehaus.org/browse/MSUREFIRE-145?page=comments#action_69330
]
Brett Porter commented on MSUREFIRE-145:
can you post the problem instead of the solution, since I think you have
misdiagnosed this.
I can't reproduce it. With:
cargoblargo
and an assertion in the test case that checks the system property, it works
with forkModes of once, never and always.
The mistaken assumptions you have above:
- isForking is true when forkMode is once and never, despite what you said.
- when forking, the system properties are passed on to surefire to set on the
child process, not set immediately. Therefore, the expression is !isForking
because you only want to set the system properties if you are *not* forking
- the logs are not misleading. The system properties are always set, just in
different JVMs.
> Plugin not longer sets system properties when forking is on and debugging
> information is not correct
>
>
> Key: MSUREFIRE-145
> URL: http://jira.codehaus.org/browse/MSUREFIRE-145
> Project: Maven 2.x Surefire Plugin
> Type: Bug
> Versions: 2.3
> Reporter: Vincent Massol
> Priority: Blocker
>
>
> The following code is in SurefirePlugin.java:
> {code:java}
> processSystemProperties( !fork.isForking() );
> if ( getLog().isDebugEnabled() )
> {
> showMap( systemProperties, "system property" );
> }
> {code}
> 2 problems:
> 1) fork.isForking() is false when forking is enabled and thus system
> properties are not set:
> {code:java}
> protected void processSystemProperties( boolean setInSystem )
> {
> [...]
> if ( setInSystem )
> {
> // Add all system properties configured by the user
> Iterator iter = systemProperties.keySet().iterator();
> while ( iter.hasNext() )
> {
> String key = (String) iter.next();
> String value = systemProperties.getProperty( key );
> System.setProperty( key, value );
> }
> }
> }
> {code}
> 2) showMap() is called regardless of whether the system properties are set
> or not, leading to the following kind of misleading logs:
> {noformat}
> [...]
> [DEBUG] Setting system property [cargo.jetty4x.port]=[8280]
> [DEBUG] Setting system property [cargo.jetty6x.port]=[8280]
> [DEBUG] Setting system property [cargo.jetty5x.port]=[8280]
> [...]
> {noformat}
> Those properties are actually NOT set.
--
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
