[jira] Created: (MNG-3411) got the error like(Searching repository for plugin with prefix: 'archetype',repository is black listed,The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not
got the error like(Searching repository for plugin with prefix: 'archetype',repository is black listed,The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exits) --- Key: MNG-3411 URL: http://jira.codehaus.org/browse/MNG-3411 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories, Command Line Affects Versions: 2.0.8 Reporter: R Priority: Blocker I start maven to use in my project but I got the errors Please help to solve this. C:\Documents and Settings\rahult4\Desktop>mvn archetype:create -DgroupId=com.myc ompany.app -DartifactId=my-app [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exi st or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: < 1 second [INFO] Finished at: Tue Feb 19 16:27:14 IST 2008 [INFO] Final Memory: 1M/2M [INFO] -- 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: (MSITE-293) Submodule inherit menu but this should not happend
[ http://jira.codehaus.org/browse/MSITE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124288 ] Arnaud commented on MSITE-293: -- I have the same probleme. I have a main modul with a site.xml like this And i dont want those item are in the submodules , please what can i do ? > Submodule inherit menu but this should not happend > -- > > Key: MSITE-293 > URL: http://jira.codehaus.org/browse/MSITE-293 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 > Environment: maven 2.0.8 > jdk 1.6 > windows >Reporter: Andreas Höhmann >Priority: Critical > > Projectstructur: > modul > | pom.xml > | src/site/site.xml > | src/site/xdoc/index.xml > +-- submodul 1 > | pom.xml > | src/site/xdoc/index.xml > +-- submodul 2 > | pom.xml > | src/site/xdoc/index.xml > modul :: site.xml > ... > > > > > > > > > > > > > >href="http://lp2p067c:82/maven2/repositories/"; /> > > > > > > ... > after "mvn clean install site" each submodules has a menu "Maven" ... but i > want this only for the "main-modul". > whats wrong? > http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html > ... Inheritance ... "By default, only the basic settings are inherited. From > the body, only the links are inherited, and these accumulate to contain all > the parents' site descriptor links." -- 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: (MSITE-261) Local Parent POM not found if specifies a directory
[
http://jira.codehaus.org/browse/MSITE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124292
]
Lukas Theussl commented on MSITE-261:
-
I have tested this with all sort of combinations I could think of, it works for
me. Please open another issue and attach a test project.
> Local Parent POM not found if specifies a directory
> --
>
> Key: MSITE-261
> URL: http://jira.codehaus.org/browse/MSITE-261
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: multi module
>Affects Versions: 2.0-beta-5
> Environment: Maven 2.0.7, JDK 1.5.0_12, WinXP SP2
>Reporter: Benjamin Bentmann
>Assignee: Lukas Theussl
>Priority: Minor
> Fix For: 2.0-beta-7
>
> Attachments: site-parent-pom.patch, site-parent-pom.patch
>
>
> The Maven core allows to specify a directory for the element
> in a module POM to locate the parent POM, e.g.{code:xml}
> ...
> ../parent
> {code}will properly find the parent POM in "../parent/pom.xml".
> However, the Site plugin does not follow this lookup strategy:{code}
> [INFO] [site:site]
> [INFO] Unable to load parent project from a relative path: Could not find the
> model file '[SNIP]\..\parent'. for project unknown
> [INFO] Parent project loaded from repository.{code}
> This log output is actually from 2.0-beta-6-SNAPSHOT, 2.0-beta-5 outputs a
> different message but fails, too.
> The attached patch fixes this although I wonder whether this functionality is
> not already included somewhere in the Maven core (where is belongs IMHO).
--
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: (MCHANGES-104) announcement-mail fails if server implements GreyListing : 451 Greylisted
announcement-mail fails if server implements GreyListing : 451 Greylisted
-
Key: MCHANGES-104
URL: http://jira.codehaus.org/browse/MCHANGES-104
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Components: announcement
Affects Versions: 2.0-beta-3
Environment: mail server implementing greylisting, maven changes
plugin 2.0-beta-4-SNAPSHOT
Reporter: Luca Dall'Olio
Our mail server implements Greylisting (see http://postgrey.schweikert.ch/help/
or http://en.wikipedia.org/wiki/Greylisting), the announcement-mail goal fails
with this message :
[INFO]
[INFO] Building base
[INFO]task-segment: [changes:announcement-mail]
[INFO]
[INFO] Preparing changes:announcement-mail
[INFO] [changes:announcement-generate]
[INFO] Creating announcement file from ./src/changes/changes.xml...
[INFO] Created template ./target/announcement/announcement.vm
[INFO] [changes:announcement-mail]
[INFO] Connecting to Host: mailhost.lan:25
[INFO] Using this sender for email announcement: [EMAIL PROTECTED] < test >
[INFO] Sending mail to [EMAIL PROTECTED]
DEBUG: JavaMail version 1.4ea
DEBUG: java.io.FileNotFoundException:
/usr/lib/jvm/java-6-sun-1.6.0.03/jre/lib/javamail.providers (No such file or
directory)
DEBUG: !anyLoaded
DEBUG: not loading resource: /META-INF/javamail.providers
DEBUG: successfully loaded resource: /META-INF/javamail.default.providers
DEBUG: Tables of loaded providers
DEBUG: Providers Listed By Class Name:
{com.sun.mail.smtp.SMTPSSLTransport=javax.mail.Provider[TRANSPORT,smtps,com.sun.mail.smtp.SMTPSSLTransport,Sun
Microsystems, Inc],
com.sun.mail.smtp.SMTPTransport=javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun
Microsystems, Inc],
com.sun.mail.imap.IMAPSSLStore=javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Sun
Microsystems, Inc],
com.sun.mail.pop3.POP3SSLStore=javax.mail.Provider[STORE,pop3s,com.sun.mail.pop3.POP3SSLStore,Sun
Microsystems, Inc],
com.sun.mail.imap.IMAPStore=javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun
Microsystems, Inc],
com.sun.mail.pop3.POP3Store=javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun
Microsystems, Inc]}
DEBUG: Providers Listed By Protocol:
{imaps=javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Sun
Microsystems, Inc],
imap=javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun
Microsystems, Inc],
smtps=javax.mail.Provider[TRANSPORT,smtps,com.sun.mail.smtp.SMTPSSLTransport,Sun
Microsystems, Inc],
pop3=javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun
Microsystems, Inc],
pop3s=javax.mail.Provider[STORE,pop3s,com.sun.mail.pop3.POP3SSLStore,Sun
Microsystems, Inc],
smtp=javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun
Microsystems, Inc]}
DEBUG: successfully loaded resource: /META-INF/javamail.default.address.map
DEBUG: !anyLoaded
DEBUG: not loading resource: /META-INF/javamail.address.map
DEBUG: java.io.FileNotFoundException:
/usr/lib/jvm/java-6-sun-1.6.0.03/jre/lib/javamail.address.map (No such file or
directory)
DEBUG: setDebug: JavaMail version 1.4ea
DEBUG: getProvider() returning
javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun
Microsystems, Inc]
DEBUG SMTP: useEhlo true, useAuth false
DEBUG SMTP: trying to connect to host "mailhost.lan", port 25, isSSL false
220 mailhost.lan ESMTP Exim 4.68 Tue, 19 Feb 2008 11:31:44 +0100
DEBUG SMTP: connected to host "mailhost.lan", port: 25
EHLO pc-test
250-mailhost.lan Hello pc-test [10.143.90.8]
250-SIZE 52428800
250-PIPELINING
250-STARTTLS
250 HELP
DEBUG SMTP: Found extension "SIZE", arg "52428800"
DEBUG SMTP: Found extension "PIPELINING", arg ""
DEBUG SMTP: Found extension "STARTTLS", arg ""
DEBUG SMTP: Found extension "HELP", arg ""
DEBUG SMTP: use8bit false
MAIL FROM:<[EMAIL PROTECTED]>
250 OK
RCPT TO:<[EMAIL PROTECTED]>
451 Greylisted, see http://postgrey.schweikert.ch/help
DEBUG SMTP: Valid Unsent Addresses
DEBUG SMTP: [EMAIL PROTECTED]
DEBUG SMTP: Sending failed because of invalid destination addresses
RSET
250 Reset OK
javax.mail.SendFailedException: Invalid Addresses;
nested exception is:
com.sun.mail.smtp.SMTPAddressFailedException: 451 Greylisted, see
http://postgrey.schweikert.ch/help
at com.sun.mail.smtp.SMTPTransport.rcptTo(SMTPTransport.java:1196)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:584)
at javax.mail.Transport.send0(Transport.java:169)
at javax.mail.Transport.send(Transport.java:98)
at
org.apache.maven.plugin.announcement.mailsender.ProjectJavamailMailSender.send(ProjectJavamailMailSender.java:193)
at
org.codehaus.plexus.mailsender.AbstractMailSender.se
[jira] Created: (MRM-704) Should be able to set the "sender" address on registration emails
Should be able to set the "sender" address on registration emails - Key: MRM-704 URL: http://jira.codehaus.org/browse/MRM-704 Project: Archiva Issue Type: Improvement Components: Users/Security Affects Versions: 1.0.1 Environment: Sun Java 1.5.0_12 Fedora Linux 2.6.21 Reporter: Andrew Heald Registration emails are sent as from [EMAIL PROTECTED] on this server. The local Exim mail server rejects this as unroutable and refuses to deliver. I'd prefer not to work around this by altering the Exim configs. Is there a way to add this to the javamail configs in plexus.xml? I'll check the source code to find out more but please let me know if this is already covered off. -- 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: (MPLUGIN-75) Internationalize PluginXdocGenerator
[ http://jira.codehaus.org/browse/MPLUGIN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPLUGIN-75. -- Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.4 fixed in r629078 > Internationalize PluginXdocGenerator > > > Key: MPLUGIN-75 > URL: http://jira.codehaus.org/browse/MPLUGIN-75 > Project: Maven 2.x Plugin Tools > Issue Type: Improvement > Components: Java Plugins, Plugin Plugin >Affects Versions: 2.3 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.4 > > -- 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: (MPLUGIN-59) [maven-plugin-testing-harness] Clean the code
[ http://jira.codehaus.org/browse/MPLUGIN-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPLUGIN-59. -- Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.4 did several cleanup > [maven-plugin-testing-harness] Clean the code > - > > Key: MPLUGIN-59 > URL: http://jira.codehaus.org/browse/MPLUGIN-59 > Project: Maven 2.x Plugin Tools > Issue Type: Bug >Reporter: Vincent Siveton >Assignee: Vincent Siveton >Priority: Trivial > Fix For: 2.4 > > > Needs to review/remove TODO in the code and specify default value in the > javadoc. -- 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: (MRM-704) Should be able to set the "sender" address on registration emails
[ http://jira.codehaus.org/browse/MRM-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Heald closed MRM-704. Resolution: Won't Fix Fix Version/s: 1.0.1 Okay, I now know this can be done in the security.properties file, so I'm closing this off. Added: [EMAIL PROTECTED] email.from.name=Archiva > Should be able to set the "sender" address on registration emails > - > > Key: MRM-704 > URL: http://jira.codehaus.org/browse/MRM-704 > Project: Archiva > Issue Type: Improvement > Components: Users/Security >Affects Versions: 1.0.1 > Environment: Sun Java 1.5.0_12 > Fedora Linux 2.6.21 >Reporter: Andrew Heald > Fix For: 1.0.1 > > > Registration emails are sent as from [EMAIL PROTECTED] on this server. The > local Exim mail server rejects this as unroutable and refuses to deliver. I'd > prefer not to work around this by altering the Exim configs. > Is there a way to add this to the javamail configs in plexus.xml? > I'll check the source code to find out more but please let me know if this is > already covered off. -- 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: (MPLUGIN-75) Internationalize PluginXdocGenerator
Internationalize PluginXdocGenerator Key: MPLUGIN-75 URL: http://jira.codehaus.org/browse/MPLUGIN-75 Project: Maven 2.x Plugin Tools Issue Type: Improvement Components: Java Plugins, Plugin Plugin Affects Versions: 2.3 Reporter: Vincent Siveton -- 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: (DOXIA-219) Bump to new release of plexus-utils
[ http://jira.codehaus.org/browse/DOXIA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed DOXIA-219. - Assignee: Vincent Siveton Resolution: Fixed done in r629097 > Bump to new release of plexus-utils > --- > > Key: DOXIA-219 > URL: http://jira.codehaus.org/browse/DOXIA-219 > Project: Maven Doxia > Issue Type: Task > Components: Decoration Model >Affects Versions: 1.0-alpha-10 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 1.0-beta-1 > > -- 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: (DOXIA-135) Handle SSI in xdoc
[
http://jira.codehaus.org/browse/DOXIA-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed DOXIA-135.
-
Resolution: Cannot Reproduce
Works now on trunk
> Handle SSI in xdoc
> --
>
> Key: DOXIA-135
> URL: http://jira.codehaus.org/browse/DOXIA-135
> Project: Maven Doxia
> Issue Type: New Feature
> Components: Module - Xdoc
>Affects Versions: 1.0-alpha-8
>Reporter: Vincent Siveton
> Fix For: 1.0-beta-1
>
>
> SSI (server side includes) are eliminated from xdoc.
> In ASF, we could use it to include ads:
> {noformat}
>
> {noformat}
--
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: (DOXIA-135) Handle SSI in xdoc
[
http://jira.codehaus.org/browse/DOXIA-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124314
]
Vincent Siveton commented on DOXIA-135:
---
Only preserve comments.
> Handle SSI in xdoc
> --
>
> Key: DOXIA-135
> URL: http://jira.codehaus.org/browse/DOXIA-135
> Project: Maven Doxia
> Issue Type: New Feature
> Components: Module - Xdoc
>Affects Versions: 1.0-alpha-8
>Reporter: Vincent Siveton
> Fix For: 1.0-beta-1
>
>
> SSI (server side includes) are eliminated from xdoc.
> In ASF, we could use it to include ads:
> {noformat}
>
> {noformat}
--
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] Reopened: (DOXIA-135) Handle SSI in xdoc
[
http://jira.codehaus.org/browse/DOXIA-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton reopened DOXIA-135:
---
reopen to fix as fixed
> Handle SSI in xdoc
> --
>
> Key: DOXIA-135
> URL: http://jira.codehaus.org/browse/DOXIA-135
> Project: Maven Doxia
> Issue Type: New Feature
> Components: Module - Xdoc
>Affects Versions: 1.0-alpha-8
>Reporter: Vincent Siveton
> Fix For: 1.0-beta-1
>
>
> SSI (server side includes) are eliminated from xdoc.
> In ASF, we could use it to include ads:
> {noformat}
>
> {noformat}
--
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: (DOXIA-224) Add source name in parser
Add source name in parser - Key: DOXIA-224 URL: http://jira.codehaus.org/browse/DOXIA-224 Project: Maven Doxia Issue Type: New Feature Components: Core Affects Versions: 1.0-alpha-10 Reporter: Vincent Siveton Should be useful when warn log are call -- 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: (DOXIA-135) Handle SSI in xdoc
[
http://jira.codehaus.org/browse/DOXIA-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed DOXIA-135.
-
Resolution: Fixed
> Handle SSI in xdoc
> --
>
> Key: DOXIA-135
> URL: http://jira.codehaus.org/browse/DOXIA-135
> Project: Maven Doxia
> Issue Type: New Feature
> Components: Module - Xdoc
>Affects Versions: 1.0-alpha-8
>Reporter: Vincent Siveton
> Fix For: 1.0-beta-1
>
>
> SSI (server side includes) are eliminated from xdoc.
> In ASF, we could use it to include ads:
> {noformat}
>
> {noformat}
--
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: (MNG-3259) Regression: Maven drops dependencies in multi-module build
[ http://jira.codehaus.org/browse/MNG-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124317 ] Ralph Goers commented on MNG-3259: -- No. You have to build it your self. To do this you need subversion installed. Then do 1. Create a directory named apache-maven-2.0.9-SNAPSHOT somewhere 2. set M2_HOME to point to the apache-maven-2.0.9-SNAPSHOT directory 3. From a directory where you want the maven source do svn co https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/ 4 cd to maven-2.0.x 5 run ./bootstrap.sh 6 add M2_HOME/bin to the beginning of your path 7 do mvn -v and verify that your version is 2.0.9-SNAPSHOT. Note that I am not claiming that anything was fixed. I just couldn't duplicate the problem on Windows with Java 5. > Regression: Maven drops dependencies in multi-module build > -- > > Key: MNG-3259 > URL: http://jira.codehaus.org/browse/MNG-3259 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.7, 2.0.8 >Reporter: Joerg Schaible >Assignee: Brian Fox >Priority: Blocker > Fix For: 2.0.9 > > Attachments: MNG-3259-2.zip, MNG-3259.zip > > Time Spent: 5 hours > Remaining Estimate: 0 minutes > > Under some circumstances Maven "forgets" about test dependencies in > multi-module builds. The affected module can be build only if the build is > started from its local project directory. If the build is run from a parent > directory, the test fails because of missing classes. This issue applies to > M207 and recent M208-RC1, the project can be build without problems with M205 > (M206 is completely bogus). The problem was for us already the show stopper > for M207 and I thought with some of the now resolved issues it has been gone, > but I was wrong. I did not report it earlier, because I was never able to > reproduce the problem with a minimal build ... until now and it took me about > 3 days to create a demonstrating multi module project. -- 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: (MWAR-146) Better support for skinny wars
[ http://jira.codehaus.org/browse/MWAR-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll closed MWAR-146. Resolution: Won't Fix There's a packagingExcludes in 2.1-alpha-2 (current trunk) It does what you want > Better support for skinny wars > -- > > Key: MWAR-146 > URL: http://jira.codehaus.org/browse/MWAR-146 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Affects Versions: 2.0.2 >Reporter: Jene Jasper > Attachments: MWAR-146-maven-war-plugin-2.0.2.patch > > > Added a warLibIncludes element to include only the specified list of jars > because the warSourceExcludes is never finished when you add new dependencies > to a project. -- 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-576) Invalid digests for http://repo1.maven.org/maven2/biz/aQute/bndlib/0.0.238/bndlib-0.0.238.pom
Invalid digests for http://repo1.maven.org/maven2/biz/aQute/bndlib/0.0.238/bndlib-0.0.238.pom - Key: MEV-576 URL: http://jira.codehaus.org/browse/MEV-576 Project: Maven Evangelism Issue Type: Bug Reporter: SebbASF The SHA1 and MD5 digests for http://repo1.maven.org/maven2/biz/aQute/bndlib/0.0.238/bndlib-0.0.238.pom don't agree with the file contents -- 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: (MAVENUPLOAD-1935) JIntellitype 1.3.1 upload
JIntellitype 1.3.1 upload - Key: MAVENUPLOAD-1935 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1935 Project: maven-upload-requests Issue Type: Task Reporter: Emil A. Lefkof III JIntellitype is a Java API for interacting with Microsoft Intellitype commands as well as registering for Global Hotkeys in your Java application. Have you ever wanted your Java application to use those special Play, Pause, and Stop media keys that are on many keyboards today? Now you can! -- 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-576) Invalid digests for http://repo1.maven.org/maven2/biz/aQute/bndlib/0.0.238/bndlib-0.0.238.pom
[ http://jira.codehaus.org/browse/MEV-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124344 ] SebbASF commented on MEV-576: - MD5 file: cb8f5b64311079a12f0cd69afccc2026 Actual: 72e6379e731e56938779cad92bfdf818 > Invalid digests for > http://repo1.maven.org/maven2/biz/aQute/bndlib/0.0.238/bndlib-0.0.238.pom > - > > Key: MEV-576 > URL: http://jira.codehaus.org/browse/MEV-576 > Project: Maven Evangelism > Issue Type: Bug >Reporter: SebbASF > > The SHA1 and MD5 digests for > http://repo1.maven.org/maven2/biz/aQute/bndlib/0.0.238/bndlib-0.0.238.pom > don't agree with the file contents -- 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-1936) Hibernate 3.2.6 ga upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124347 ] Dan Tran commented on MAVENUPLOAD-1936: --- where is the bundle? > Hibernate 3.2.6 ga upload > - > > Key: MAVENUPLOAD-1936 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1936 > Project: maven-upload-requests > Issue Type: Task >Reporter: Emil A. Lefkof III > > Not a member of the Hibernate team but thought the new 3.2.6 ga should be > uploaded to ibiblio -- 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: (MNG-3412) State of Maven Embedder and documentation
State of Maven Embedder and documentation - Key: MNG-3412 URL: http://jira.codehaus.org/browse/MNG-3412 Project: Maven 2 Issue Type: Bug Components: Embedding Reporter: Dimitry Voytenko Is Meven Embedder project still alive? The documentation in http://maven.apache.org/guides/mini/guide-embedding-m2.html doesn't match org.apache.maven/maven-embedder artifact at all (I tried against 2.0.4 version). -- 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: (MRM-705) database scanning should be able to be run after repository scanning
[ http://jira.codehaus.org/browse/MRM-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-705: - Fix Version/s: 1.x > database scanning should be able to be run after repository scanning > > > Key: MRM-705 > URL: http://jira.codehaus.org/browse/MRM-705 > Project: Archiva > Issue Type: Improvement > Components: repository scanning >Affects Versions: 1.0.1 >Reporter: Brett Porter > Fix For: 1.x > > > since after the initial processing both scans are quite fast, being able to > put them together sequentially makes sense so that changes are reflected as > quickly as 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] Commented: (MRELEASE-186) Active profiles are not carried through into the release descriptor
[ http://jira.codehaus.org/browse/MRELEASE-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124345 ] Rohnny Moland commented on MRELEASE-186: This should also update the version of local dependencies defined inside a profile, or a dependency to a plugin inside a profile. > Active profiles are not carried through into the release descriptor > --- > > Key: MRELEASE-186 > URL: http://jira.codehaus.org/browse/MRELEASE-186 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 >Reporter: Jason van Zyl >Assignee: Jason van Zyl > > When using a profile for a release it is not passed on in the > release.properties so it's not executed in the perform goal. -- 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-1936) Hibernate 3.2.6 ga upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124348 ] Emil A. Lefkof III commented on MAVENUPLOAD-1936: - Sorry I forgot to put NOT A DEVELOPER on the Contributor URL. Just posting this to make sure it gets on the radar for them to upload. It was released on Feb 7th. > Hibernate 3.2.6 ga upload > - > > Key: MAVENUPLOAD-1936 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1936 > Project: maven-upload-requests > Issue Type: Task >Reporter: Emil A. Lefkof III > > Not a member of the Hibernate team but thought the new 3.2.6 ga should be > uploaded to ibiblio -- 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: (MAVENUPLOAD-1936) Hibernate 3.2.6 ga upload
Hibernate 3.2.6 ga upload - Key: MAVENUPLOAD-1936 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1936 Project: maven-upload-requests Issue Type: Task Reporter: Emil A. Lefkof III Not a member of the Hibernate team but thought the new 3.2.6 ga should be uploaded to ibiblio -- 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: (MRM-705) database scanning should be able to be run after repository scanning
database scanning should be able to be run after repository scanning Key: MRM-705 URL: http://jira.codehaus.org/browse/MRM-705 Project: Archiva Issue Type: Improvement Components: repository scanning Affects Versions: 1.0.1 Reporter: Brett Porter since after the initial processing both scans are quite fast, being able to put them together sequentially makes sense so that changes are reflected as quickly as 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] Commented: (MAVENUPLOAD-1936) Hibernate 3.2.6 ga upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124352 ] Dan Tran commented on MAVENUPLOAD-1936: --- you are freely to submit the bundle, with out this the maven central's "gate keeper" will close this issue :-) > Hibernate 3.2.6 ga upload > - > > Key: MAVENUPLOAD-1936 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1936 > Project: maven-upload-requests > Issue Type: Task >Reporter: Emil A. Lefkof III > > Not a member of the Hibernate team but thought the new 3.2.6 ga should be > uploaded to ibiblio -- 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: (MNG-3413) Allow plugins to be downloaded from standard repository
Allow plugins to be downloaded from standard repository --- Key: MNG-3413 URL: http://jira.codehaus.org/browse/MNG-3413 Project: Maven 2 Issue Type: Improvement Components: Dependencies, Plugins and Lifecycle, Settings Reporter: Paul Gier Priority: Minor I would like to be able to define a single repository either in settings.xml or in my pom that can be used for downloading both project dependencies and plugins. In many situations the regular repository and the plugin repository are the same place, so it would be nice to be able to do something like this: snapshots.mydomain.com My snapshot repository http://snapshots.mydomain.com/ true false true This would allow me to download snapshots of both project dependencies and plugins from the repository without needing to configure a separate plugin 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] Created: (MAVENUPLOAD-1937) Upload JASIG CAS Client for Java 3.1.1
Upload JASIG CAS Client for Java 3.1.1 -- Key: MAVENUPLOAD-1937 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1937 Project: maven-upload-requests Issue Type: Wish Reporter: Scott Battaglia http://www.ja-sig.org/downloads/cas-clients/maven-upload-requests/cas-client-core-3.1.1-bundle.jar http://www.jasig.org/products/cas/ http://www.ja-sig.org/products/cas/about/index.html I'm a developer on the JASIG CAS Client project and would like to use the groupId org.jasig.cas -- 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: (MAVENUPLOAD-1938) Upload Annsor to the Maven Central Repository.
Upload Annsor to the Maven Central Repository. -- Key: MAVENUPLOAD-1938 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1938 Project: maven-upload-requests Issue Type: Wish Reporter: Richard Burton Attachments: annsor-core-1.0.3-bundle.jar, annsor-core-1.0.3-sources.jar, annsor-core-1.0.3.jar, pom.xml Annsor is a lightweight runtime annotation processor. The purpose of Annsor is to simplify processing of Annotations during runtime, without sacrificing performance or affecting your API. Thank you, Richard L. Burton III -- 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: (MPLUGIN-35) Generated documentation for @phase is misleading
[ http://jira.codehaus.org/browse/MPLUGIN-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124371 ] Dennis Lundberg commented on MPLUGIN-35: I have committed the improved text supplied by Benjamin. Due to MPLUGIN-75 now being fixed, we should also update the French translation in pluginxdoc_fr.properties. I don't speak French, but I understand enough to see that it needs to be updated. Vincent, can you do that? > Generated documentation for @phase is misleading > > > Key: MPLUGIN-35 > URL: http://jira.codehaus.org/browse/MPLUGIN-35 > Project: Maven 2.x Plugin Tools > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Matthew Beermann >Priority: Minor > Fix For: 2.4 > > Attachments: phase-binding.patch > > > If you have the @phase annotation in your mojo, the generated documentation > will look something like: "Automatically executes within the lifecycle phase: > validate " > This is misleading; the goal will _not_ automatically execute - very few > goals in Maven do. Instead, you need an section in your POM. I > think it would be clearer to just say "Executes during the lifecycle phase: > validate" or something like that. -- 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-1938) Upload Annsor to the Maven Central Repository.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Burton updated MAVENUPLOAD-1938: Attachment: pom.xml The parent POM > Upload Annsor to the Maven Central Repository. > -- > > Key: MAVENUPLOAD-1938 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1938 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Richard Burton > Attachments: annsor-core-1.0.3-bundle.jar, > annsor-core-1.0.3-sources.jar, annsor-core-1.0.3.jar, pom.xml > > > Annsor is a lightweight runtime annotation processor. The purpose of Annsor > is to simplify processing of Annotations during runtime, without sacrificing > performance or affecting your API. > Thank you, > Richard L. Burton III -- 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: (MINVOKER-23) Use project.getProperties() when performing IT pom interpolations
[
http://jira.codehaus.org/browse/MINVOKER-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MINVOKER-23.
Assignee: Olivier Lamy (was: John Casey)
Resolution: Fixed
fixed in rev 629249.
Thanks
> Use project.getProperties() when performing IT pom interpolations
> -
>
> Key: MINVOKER-23
> URL: http://jira.codehaus.org/browse/MINVOKER-23
> Project: Maven 2.x Invoker Plugin
> Issue Type: Improvement
>Affects Versions: 1.1
>Reporter: John Allen
>Assignee: Olivier Lamy
> Attachments: MINVOKER-23.diff
>
>
> Although some excellent work has been to allow for various scheme of
> interpolation to be employed it would be very beneficial if the
> buildInterpolatedPomFile method also would use, optionally if you wish, the
> project's own properties and not just the supplied
> parameter values.
> Simple use case:
> Using the [maven-component-it-plugin to inject the project's local
> repository|https://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/maven-component-it-plugin]
> path into the project's main properties would then allow us to use this
> value to build a simple 'local repository as a main repository'
> into the IT plugin POMS which would allow us to greatly speed up testing.
> The [assembly
> plugin|https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-assembly-plugin/pom.xml]
> currently jumps through the hoops of filtering and installing a special IT
> parent pom project to interpolate this 'local repo property value' into a POM
> and then the IT poms use this parent and thus have access to the special
> repository of the form:
>
>
> main.local.as.remote
> file://${local.repo.path}
>
>
>
>
> main.local.as.remote
> file://${local.repo.path}
>
>
> If the invoker was willing to use the main project's Properties as well as
> the explicitly defined in interpolation we could
> remove the need for this filtering and installing and simply get the job done
> from in one simple call.
--
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: (MPLUGIN-76) Fixed file encoding employed by PluginXDocGenerator
Fixed file encoding employed by PluginXDocGenerator --- Key: MPLUGIN-76 URL: http://jira.codehaus.org/browse/MPLUGIN-76 Project: Maven 2.x Plugin Tools Issue Type: Bug Components: API Affects Versions: 2.3 Reporter: Benjamin Bentmann Attachments: file-encoding.patch The class currenlty uses the platform's default encoding (say ISO-8859-1) to write a XML file without a XML declaration such that readers will assume UTF-8 instead. The patch enforces UTF-8 output and (as a best practice) adds the XML declaration to the output file. -- 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: (MINVOKER-21) Clean up IT test output when running mvn clean.
[ http://jira.codehaus.org/browse/MINVOKER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124387 ] Paul Gier commented on MINVOKER-21: --- Yes, using that option works fine for me too. If you want you can close the issue or schedule it for an undefined future release if you think having a clean mojo would be useful. > Clean up IT test output when running mvn clean. > --- > > Key: MINVOKER-21 > URL: http://jira.codehaus.org/browse/MINVOKER-21 > Project: Maven 2.x Invoker Plugin > Issue Type: New Feature >Affects Versions: 1.1 >Reporter: Paul Gier > Fix For: 1.2 > > > Not sure if there is an easy way to do this, but it would be nice if the > invoker plugin could be set up so that during a "mvn clean" the target > directories and the build.log created by the integration tests would be > cleaned up. -- 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: (MINVOKER-21) Clean up IT test output when running mvn clean.
[
http://jira.codehaus.org/browse/MINVOKER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MINVOKER-21.
Assignee: Olivier Lamy
Resolution: Won't Fix
workaround is to use
{code:xml}
${project.build.directory}/it
{code}
> Clean up IT test output when running mvn clean.
> ---
>
> Key: MINVOKER-21
> URL: http://jira.codehaus.org/browse/MINVOKER-21
> Project: Maven 2.x Invoker Plugin
> Issue Type: New Feature
>Affects Versions: 1.1
>Reporter: Paul Gier
>Assignee: Olivier Lamy
> Fix For: 1.2
>
>
> Not sure if there is an easy way to do this, but it would be nice if the
> invoker plugin could be set up so that during a "mvn clean" the target
> directories and the build.log created by the integration tests would be
> cleaned up.
--
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: (MPLUGIN-74) Explicitly control layout of tables generated for parameters of mojo description
[
http://jira.codehaus.org/browse/MPLUGIN-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MPLUGIN-74.
--
Assignee: Dennis Lundberg
Resolution: Fixed
Fix Version/s: 2.4
Patch applied. Thanks!
> Explicitly control layout of tables generated for parameters of mojo
> description
>
>
> Key: MPLUGIN-74
> URL: http://jira.codehaus.org/browse/MPLUGIN-74
> Project: Maven 2.x Plugin Tools
> Issue Type: Task
> Components: API
>Affects Versions: 2.3
>Reporter: Benjamin Bentmann
>Assignee: Dennis Lundberg
>Priority: Trivial
> Fix For: 2.4
>
> Attachments: table-style.patch
>
>
> The handling for the {{}} element in [commit 578469 to
> doxia-module-xdoc|http://svn.apache.org/viewvc/maven/doxia/doxia/trunk/doxia-modules/doxia-module-xdoc/src/main/java/org/apache/maven/doxia/module/xdoc/XdocParser.java?r1=571451&r2=578469&pathrev=578469]
> will cause a change for the current output of the PluginXdocGenerator (i.e.
> table cells get centered instead of left aligned and a border will be
> rendered). Updating the XDoc generator now should allow a smooth transition
> to doxia 1.0-beta-1.
--
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: (MPLUGIN-77) Add german translation
Add german translation -- Key: MPLUGIN-77 URL: http://jira.codehaus.org/browse/MPLUGIN-77 Project: Maven 2.x Plugin Tools Issue Type: Improvement Components: API Affects Versions: 2.3 Reporter: Benjamin Bentmann Priority: Minor Attachments: i18n-de.patch Teaching the report another language. -- 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: (MINVOKER-21) Clean up IT test output when running mvn clean.
[ http://jira.codehaus.org/browse/MINVOKER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124378 ] Olivier Lamy commented on MINVOKER-21: -- I'm tempted to say won't fix because the benjamin's comment is a good idea and do the job. Paul have you try that ? > Clean up IT test output when running mvn clean. > --- > > Key: MINVOKER-21 > URL: http://jira.codehaus.org/browse/MINVOKER-21 > Project: Maven 2.x Invoker Plugin > Issue Type: New Feature >Affects Versions: 1.1 >Reporter: Paul Gier > Fix For: 1.2 > > > Not sure if there is an easy way to do this, but it would be nice if the > invoker plugin could be set up so that during a "mvn clean" the target > directories and the build.log created by the integration tests would be > cleaned up. -- 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: (MPLUGIN-76) Fixed file encoding employed by PluginXDocGenerator
[
http://jira.codehaus.org/browse/MPLUGIN-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124395
]
Benjamin Bentmann commented on MPLUGIN-76:
--
Well, in the end, it's quit the same code, i.e. an OutputStreamWriter on top of
a FileOutputStream. What I don't like about {{WriterFactory.newWriter()} is
that its method signature ony returns a {{Writer}} though it could have been
declared to return {{OutputStreamWriter}} which is a little more convenient in
use (especially it offers {{getEncoding()}}). For some funny thing,
{{WriterFactory.newXmlWriter()}} does not return only {{Writer}}...
> Fixed file encoding employed by PluginXDocGenerator
> ---
>
> Key: MPLUGIN-76
> URL: http://jira.codehaus.org/browse/MPLUGIN-76
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: API
>Affects Versions: 2.3
>Reporter: Benjamin Bentmann
> Attachments: file-encoding.patch
>
>
> The class currenlty uses the platform's default encoding (say ISO-8859-1) to
> write a XML file without a XML declaration such that readers will assume
> UTF-8 instead. The patch enforces UTF-8 output and (as a best practice) adds
> the XML declaration to the output file.
--
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] Issue Comment Edited: (MPLUGIN-76) Fixed file encoding employed by PluginXDocGenerator
[
http://jira.codehaus.org/browse/MPLUGIN-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124395
]
bentmann edited comment on MPLUGIN-76 at 2/19/08 5:11 PM:
---
Well, in the end, it's quit the same code, i.e. an OutputStreamWriter on top of
a FileOutputStream. What I don't like about {{WriterFactory.newWriter()}} is
that its method signature ony returns a {{Writer}} though it could have been
declared to return {{OutputStreamWriter}} which is a little more convenient in
use (especially it offers {{getEncoding()}}). For some funny thing,
{{WriterFactory.newXmlWriter()}} does not return only {{Writer}}...
was (Author: bentmann):
Well, in the end, it's quit the same code, i.e. an OutputStreamWriter on
top of a FileOutputStream. What I don't like about {{WriterFactory.newWriter()}
is that its method signature ony returns a {{Writer}} though it could have been
declared to return {{OutputStreamWriter}} which is a little more convenient in
use (especially it offers {{getEncoding()}}). For some funny thing,
{{WriterFactory.newXmlWriter()}} does not return only {{Writer}}...
> Fixed file encoding employed by PluginXDocGenerator
> ---
>
> Key: MPLUGIN-76
> URL: http://jira.codehaus.org/browse/MPLUGIN-76
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: API
>Affects Versions: 2.3
>Reporter: Benjamin Bentmann
> Attachments: file-encoding.patch
>
>
> The class currenlty uses the platform's default encoding (say ISO-8859-1) to
> write a XML file without a XML declaration such that readers will assume
> UTF-8 instead. The patch enforces UTF-8 output and (as a best practice) adds
> the XML declaration to the output file.
--
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: (MPLUGIN-76) Fixed file encoding employed by PluginXDocGenerator
[ http://jira.codehaus.org/browse/MPLUGIN-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124391 ] Vincent Siveton commented on MPLUGIN-76: Better should be to use WriterFactory.newWriter( file, encoding ) > Fixed file encoding employed by PluginXDocGenerator > --- > > Key: MPLUGIN-76 > URL: http://jira.codehaus.org/browse/MPLUGIN-76 > Project: Maven 2.x Plugin Tools > Issue Type: Bug > Components: API >Affects Versions: 2.3 >Reporter: Benjamin Bentmann > Attachments: file-encoding.patch > > > The class currenlty uses the platform's default encoding (say ISO-8859-1) to > write a XML file without a XML declaration such that readers will assume > UTF-8 instead. The patch enforces UTF-8 output and (as a best practice) adds > the XML declaration to the output file. -- 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: (MINVOKER-23) Use project.getProperties() when performing IT pom interpolations
[
http://jira.codehaus.org/browse/MINVOKER-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MINVOKER-23:
-
Fix Version/s: 1.2
> Use project.getProperties() when performing IT pom interpolations
> -
>
> Key: MINVOKER-23
> URL: http://jira.codehaus.org/browse/MINVOKER-23
> Project: Maven 2.x Invoker Plugin
> Issue Type: Improvement
>Affects Versions: 1.1
>Reporter: John Allen
>Assignee: Olivier Lamy
> Fix For: 1.2
>
> Attachments: MINVOKER-23.diff
>
>
> Although some excellent work has been to allow for various scheme of
> interpolation to be employed it would be very beneficial if the
> buildInterpolatedPomFile method also would use, optionally if you wish, the
> project's own properties and not just the supplied
> parameter values.
> Simple use case:
> Using the [maven-component-it-plugin to inject the project's local
> repository|https://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/maven-component-it-plugin]
> path into the project's main properties would then allow us to use this
> value to build a simple 'local repository as a main repository'
> into the IT plugin POMS which would allow us to greatly speed up testing.
> The [assembly
> plugin|https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-assembly-plugin/pom.xml]
> currently jumps through the hoops of filtering and installing a special IT
> parent pom project to interpolate this 'local repo property value' into a POM
> and then the IT poms use this parent and thus have access to the special
> repository of the form:
>
>
> main.local.as.remote
> file://${local.repo.path}
>
>
>
>
> main.local.as.remote
> file://${local.repo.path}
>
>
> If the invoker was willing to use the main project's Properties as well as
> the explicitly defined in interpolation we could
> remove the need for this filtering and installing and simply get the job done
> from in one simple call.
--
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: (MPLUGIN-48) Required parameters of self written Mojo configured in execution part of POM are ignored and causing error
[
http://jira.codehaus.org/browse/MPLUGIN-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MPLUGIN-48:
---
Description:
Required parameters configured in execution part of POM are ignored if:
the parameter ist set as required AND
(no default value is set OR
default-Value is set to "") AND
configuration of parameter values are done in the execution element.
Example:
Parameter definition in Mojo:
{code}
/**
* @parameter default-value="ATTENTION DEFAULT"
* @required
*/
private File dummy1;
{code}
and snip from POM:
{code:xml}
myownartifact.plugin
maven-myownartifact-plugin
true
extract
c:/my files/test/dummy1
extract
{code}
runs fine.
If I change the definition of the parameter to
{code}
/**
* @parameter
* @required
*/
private File dummy1;
{code}
or
{code}
* @parameter default-value=""
{code}
then I got an error:
[0] inside the definition for plugin: 'maven-myownartifact-plugin'specify the
following:
...
VALUE
.
In my opinion this is a bug because with @required I have already tagged this
parameter as mandatory. So I'm already forced to configure it.
BTW, if I configure the parameters outside the execution element evrything
works fine as expected!
More info:
- the plugin is bind to the package phase
If a runable example is needed it's possible to provide one.
was:
Required parameters configured in execution part of POM are ignored if:
the parameter ist set as required AND
(no default value is set OR
default-Value is set to "") AND
configuration of parameter values are done in the execution element.
Example:
Parameter definition in Mojo:
/**
* @parameter default-value="ATTENTION DEFAULT"
* @required
*/
private File dummy1;
and snip from POM:
myownartifact.plugin
maven-myownartifact-plugin
true
extract
c:/my files/test/dummy1
extract
runs fine.
If I change the definition of the parameter to
/**
* @parameter
* @required
*/
private File dummy1;
or
* @parameter default-value=""
then I got an error:
[0] inside the definition for plugin: 'maven-myownartifact-plugin'specify the
following:
...
VALUE
.
In my opinion this is a bug because with @required I have already tagged this
parameter as mandatory. So I'm already forced to configure it.
BTW, if I configure the parameters outside the execution element evrything
works fine as expected!
More info:
- the plugin is bind to the package phase
If a runable example is needed it's possible to provide one.
> Required parameters of self written Mojo configured in execution part of POM
> are ignored and causing error
> --
>
> Key: MPLUGIN-48
> URL: http://jira.codehaus.org/browse/MPLUGIN-48
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Environment: Windows XP
>Reporter: Halil-Cem Gürsoy
>
> Required parameters configured in execution part of POM are ignored if:
> the parameter ist set as required AND
> (no default value is set OR
> default-Value is set to "") AND
> configuration of parameter values are done in the execution element.
> Example:
> Parameter definition in Mojo:
> {code}
> /**
>* @parameter default-value="ATTENTION DEFAULT"
>* @required
>*/
> private File dummy1;
> {code}
> and snip from POM:
> {code:xml}
>
>
> myownartifact.plugin
> maven-myownartifact-plugin
> true
>
>
> extract
>
> c:/my files/test/dummy1
>
>
>extract
>
>
>
>
>
> {code}
> runs fine.
> If I change the definition of the parameter to
> {code}
> /**
>* @parameter
>* @required
>*/
> private File dummy1;
> {code}
> or
> {code}
> * @parameter default-value=""
> {code}
> then I got an error:
> [0] inside the definition for plugin: 'maven-myownartifact-plugin'specify the
> following:
>
> ...
> VALUE
> .
> In my opinion this is a bug because with @required I have already tagged this
> parameter as mandatory. So I'm already forced to configure it.
> BTW, if I configure the parameters outside
[jira] Updated: (MPLUGIN-55) Maven (plexus?) doesn't recognize Mojo parameter setters defined in a base class
[
http://jira.codehaus.org/browse/MPLUGIN-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MPLUGIN-55:
---
Description:
Create a Mojo class that extends some base class that itself defines a
parameter that uses a setter. Here's an example:
{code}
public class Base extends AbstractMojo
{
/**
* @parameter property="parameter"
*/
private String m_parameter;
public void setParameter(String parameter)
{
m_parameter = parameter;
}
...
}
{code}
{code}
/**
* @goal mygoal
*/
public class MyMojo extends Base
{
...
}
{code}
Maven can build the plugin just fine, but when I attempt to execute the goal, I
get an error:
org.codehaus.plexus.component.configurator.ComponentConfigurationException:
Cannot access method: com.example.MyMojo.setParameter( java.lang.Class ).
If I move the setter to the goal class, it works just fine. Maven (plexus?)
should be able to access the method from the base class.
was:
Create a Mojo class that extends some base class that itself defines a
parameter that uses a setter. Here's an example:
public class Base extends AbstractMojo
{
/**
* @parameter property="parameter"
*/
private String m_parameter;
public void setParameter(String parameter)
{
m_parameter = parameter;
}
...
}
/**
* @goal mygoal
*/
public class MyMojo extends Base
{
...
}
Maven can build the plugin just fine, but when I attempt to execute the goal, I
get an error:
org.codehaus.plexus.component.configurator.ComponentConfigurationException:
Cannot access method: com.example.MyMojo.setParameter( java.lang.Class ).
If I move the setter to the goal class, it works just fine. Maven (plexus?)
should be able to access the method from the base class.
> Maven (plexus?) doesn't recognize Mojo parameter setters defined in a base
> class
>
>
> Key: MPLUGIN-55
> URL: http://jira.codehaus.org/browse/MPLUGIN-55
> Project: Maven 2.x Plugin Tools
> Issue Type: Improvement
>Reporter: David Jackman
>Priority: Minor
>
> Create a Mojo class that extends some base class that itself defines a
> parameter that uses a setter. Here's an example:
> {code}
> public class Base extends AbstractMojo
> {
>/**
>* @parameter property="parameter"
>*/
>private String m_parameter;
>public void setParameter(String parameter)
>{
> m_parameter = parameter;
>}
> ...
> }
> {code}
> {code}
> /**
> * @goal mygoal
> */
> public class MyMojo extends Base
> {
> ...
> }
> {code}
> Maven can build the plugin just fine, but when I attempt to execute the goal,
> I get an error:
> org.codehaus.plexus.component.configurator.ComponentConfigurationException:
> Cannot access method: com.example.MyMojo.setParameter( java.lang.Class ).
> If I move the setter to the goal class, it works just fine. Maven (plexus?)
> should be able to access the method from the base class.
--
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: (MPLUGIN-15) Support includes/excludes
[ http://jira.codehaus.org/browse/MPLUGIN-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MPLUGIN-15: --- Description: Support advanced scanner configuration (e.g. includes/excludes), just like the compiler plugin does. This allows to restrict the sources the plugin scans, rationale see compiler plugin. This also would help working around QDOX not supporting JDK 1.5 (see [1] and [2]). If this is wanted and somebody tells me the best way, I'll gladly implement it. I looked at the code and noticed a "brute force" approach would mean adding the scanner configuration to the plugin MOJO and propagating it through MojoScanner.populatePluginDescriptor and MojoDescriptorExtractor.execute (changing the intefaces). Does not sound like the best option... The next thing would be to add the configuration to PluginDescriptor (maybe other plugins might want to use this feature, too..). The third option would be to add it to some component manager that is available, but escaped me while looking at the code. Any suggestions? [1] MPLUGIN-1 [2] QDOX-94 was: Support advanced scanner configuration (e.g. includes/excludes), just like the compiler plugin does. This allows to restrict the sources the plugin scans, rationale see compiler plugin. This also would help working around QDOX not supporting JDK 1.5 (see [1] and [2]). If this is wanted and somebody tells me the best way, I'll gladly implement it. I looked at the code and noticed a "brute force" approach would mean adding the scanner configuration to the plugin MOJO and propagating it through MojoScanner.populatePluginDescriptor and MojoDescriptorExtractor.execute (changing the intefaces). Does not sound like the best option... The next thing would be to add the configuration to PluginDescriptor (maybe other plugins might want to use this feature, too..). The third option would be to add it to some component manager that is available, but escaped me while looking at the code. Any suggestions? [1] http://jira.codehaus.org/browse/MPLUGIN-1 [2] http://jira.codehaus.org/browse/QDOX-94 > Support includes/excludes > - > > Key: MPLUGIN-15 > URL: http://jira.codehaus.org/browse/MPLUGIN-15 > Project: Maven 2.x Plugin Tools > Issue Type: Improvement >Reporter: Jochen Kuhnle > > Support advanced scanner configuration (e.g. includes/excludes), just like > the compiler plugin does. This allows to restrict the sources the plugin > scans, rationale see compiler plugin. > This also would help working around QDOX not supporting JDK 1.5 (see [1] and > [2]). > If this is wanted and somebody tells me the best way, I'll gladly implement > it. I looked at the code and noticed a "brute force" approach would mean > adding the scanner configuration to the plugin MOJO and propagating it > through MojoScanner.populatePluginDescriptor and > MojoDescriptorExtractor.execute (changing the intefaces). Does not sound > like the best option... The next thing would be to add the configuration to > PluginDescriptor (maybe other plugins might want to use this feature, too..). > The third option would be to add it to some component manager that is > available, but escaped me while looking at the code. > Any suggestions? > [1] MPLUGIN-1 > [2] QDOX-94 -- 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: (MPLUGIN-35) Generated documentation for @phase is misleading
[ http://jira.codehaus.org/browse/MPLUGIN-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPLUGIN-35. -- Assignee: Vincent Siveton Resolution: Fixed Added the French translation > Generated documentation for @phase is misleading > > > Key: MPLUGIN-35 > URL: http://jira.codehaus.org/browse/MPLUGIN-35 > Project: Maven 2.x Plugin Tools > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Matthew Beermann >Assignee: Vincent Siveton >Priority: Minor > Fix For: 2.4 > > Attachments: phase-binding.patch > > > If you have the @phase annotation in your mojo, the generated documentation > will look something like: "Automatically executes within the lifecycle phase: > validate " > This is misleading; the goal will _not_ automatically execute - very few > goals in Maven do. Instead, you need an section in your POM. I > think it would be clearer to just say "Executes during the lifecycle phase: > validate" or something like that. -- 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: (MPLUGIN-44) archetype:create strips out comments from the template pom.xml..
[ http://jira.codehaus.org/browse/MPLUGIN-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124402 ] Dennis Lundberg commented on MPLUGIN-44: Does this issue really have anything to do with "Maven 2.x Plugin Tools", or can it be moved to "Maven Archetype"? > archetype:create strips out comments from the template pom.xml.. > > > Key: MPLUGIN-44 > URL: http://jira.codehaus.org/browse/MPLUGIN-44 > Project: Maven 2.x Plugin Tools > Issue Type: Bug > Environment: maven-archetype-plugin 1.0-alpha-4 (as stated on IRC) >Reporter: Prasad Kashyap > > archetype:create strips out comments from the template pom.xml. > comments and license headers from the template pom.xml are gone in the newly > created project -- 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-1920) Synchronize Central with OPS4J release repository.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1920. --- Assignee: Carlos Sanchez Resolution: Fixed > Synchronize Central with OPS4J release repository. > -- > > Key: MAVENUPLOAD-1920 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1920 > Project: maven-upload-requests > Issue Type: Task >Reporter: Niclas Hedhman >Assignee: Carlos Sanchez > Attachments: ops4j.sh > > > OPS4J is an umbrella of many projects, and users are now starting to request > that we upload our releases to Maven Central for convenience. > My involvement is extensive, and the easiest proof is "whois ops4j.org" > The public Maven ssh key has been added to the .ssh/authorized_keys, but I > can't validate that nothing gone wrong. > We are opening a new repository just for this purpose, to make sure that no > garbage comes along. We have not added anything in there yet. > A script has been attached. -- 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-1911) Sync sf.net.patterntesting repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1911. --- Assignee: Carlos Sanchez Resolution: Fixed > Sync sf.net.patterntesting repository > - > > Key: MAVENUPLOAD-1911 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1911 > Project: maven-upload-requests > Issue Type: Task >Reporter: Oliver Boehm >Assignee: Carlos Sanchez > Attachments: net.sf.patterntesting.sh > > > Please synchronize http://patterntesting.sourceforge.net/m2/repository/ to > the central maven 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] Closed: (MAVENUPLOAD-1928) Please synchronize HDIV repository (a script has been attached) to the central maven repository.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1928. --- Assignee: Carlos Sanchez Resolution: Fixed > Please synchronize HDIV repository (a script has been attached) to the > central maven repository. > > > Key: MAVENUPLOAD-1928 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1928 > Project: maven-upload-requests > Issue Type: Task >Reporter: Gorka Vicente >Assignee: Carlos Sanchez > Attachments: org.hdiv.sh > > -- 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-1926) add org.wickettools.extjs to automatically synced repositories
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1926. --- Resolution: Fixed > add org.wickettools.extjs to automatically synced repositories > -- > > Key: MAVENUPLOAD-1926 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1926 > Project: maven-upload-requests > Issue Type: Task >Reporter: Jeremy Fergason > Attachments: org.wickettools.extjs.sh > > > Please add the org.wicettools.extjs to the list of automatically synched > repositories. > Here's proof of domain ownership: > NOTICE: Access to .ORG WHOIS information is provided to assist persons in > determining the contents of a domain name registration record in the Public > Interest > Registry > registry database. The data in this record is provided by Public Interest > Registry > for informational purposes only, and Public Interest Registry does not > guarantee its > accuracy. This service is intended only for query-based access. You agree > that you will use this data only for lawful purposes and that, under no > circumstances will you use this data to: (a) allow, enable, or otherwise > support the transmission by e-mail, telephone, or facsimile of mass > unsolicited, commercial advertising or solicitations to entities other than > the data recipient's own existing customers; or (b) enable high volume, > automated, electronic processes that send queries or data to the systems of > Registry Operator or any ICANN-Accredited Registrar, except as reasonably > necessary to register domain names or modify existing registrations. All > rights reserved. Public Interest Registry reserves the right to modify these > terms at any > time. By submitting this query, you agree to abide by this policy. > Domain ID:D150589766-LROR > Domain Name:WICKETTOOLS.ORG > Created On:09-Jan-2008 02:08:47 UTC > Expiration Date:09-Jan-2009 02:08:47 UTC > Sponsoring Registrar:OnlineNIC Inc. (R64-LROR) > Status:TRANSFER PROHIBITED > Registrant ID:ONLC-3128647-4 > Registrant Name:Jeremy Fergason > Registrant Organization:Corwynn Technology > Registrant Street1: > Registrant Street2: > Registrant Street3: > Registrant City: > Registrant State/Province: > Registrant Postal Code: > Registrant Country: > Registrant Phone: > Registrant Phone Ext.: > Registrant FAX:+1.5207956998 > Registrant FAX Ext.: > Registrant Email:[EMAIL PROTECTED] > Admin ID:ONLC-3128647-1 > Admin Name:Jeremy Fergason > Admin Organization:Corwynn Technology > Admin Street1: > Admin Street2: > Admin Street3: > Admin City: > Admin State/Province: > Admin Postal Code: > Admin Country: > Admin Phone: > Admin Phone Ext.: > Admin FAX:+1.5207956998 > Admin FAX Ext.: > Admin Email:[EMAIL PROTECTED] > Tech ID:ONLC-3128647-2 > Tech Name:Jeremy Fergason > Tech Organization:Corwynn Technology > Tech Street1: > Tech Street2: > Tech Street3: > Tech City: > Tech State/Province: > Tech Postal Code: > Tech Country:US > Tech Phone: > Tech Phone Ext.: > Tech FAX:+1.5207956998 > Tech FAX Ext.: > Tech Email:[EMAIL PROTECTED] > Name Server:NS1.DNS-DIY.NET > Name Server:NS2.DNS-DIY.NET > Name Server: > Name Server: > Name Server: > Name Server: > Name Server: > Name Server: > Name Server: > Name Server: > Name Server: > Name Server: > Name Server: -- 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-1933) Please add sync script for de.sven-jacobs.loremipsum
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1933. --- Assignee: Carlos Sanchez Resolution: Fixed > Please add sync script for de.sven-jacobs.loremipsum > > > Key: MAVENUPLOAD-1933 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1933 > Project: maven-upload-requests > Issue Type: Task >Reporter: Sven Jacobs >Assignee: Carlos Sanchez > Attachments: de.sven-jacobs.loremipsum.sh > > > Please add the attached sync script to the Maven 2 repo. > PROOF: http://loremipsum.sven-jacobs.de redirects to project website at > http://loremipsum.sourceforge.net/. My name, Sven Jacons, is mentioned on > that page. -- 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-574) Incorrect metadata from java.xml
[ http://jira.codehaus.org/browse/MEV-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-574. -- Assignee: Carlos Sanchez Resolution: Fixed > Incorrect metadata from java.xml > > > Key: MEV-574 > URL: http://jira.codehaus.org/browse/MEV-574 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid Metadata >Reporter: Adrian Skehill >Assignee: Carlos Sanchez > > The maven-metadata for the javax.mail component is incorrect. > When I open the metadata xml file it says: > (http://repo1.maven.org/maven2/javax/mail/mail/maven-metadata.xml) > javax.activation > mail > But this should be > javax.mail > mail -- 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-1912) Upload jstl-1.2.jar to central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1912. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload jstl-1.2.jar to central > -- > > Key: MAVENUPLOAD-1912 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1912 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Ignacio Coloma >Assignee: Carlos Sanchez > > The correct group ID has already been created at javax.servlet/jstl, but the > jar file is missing (only the pom and source bundle have been deployed). > Please include to make it usable. > This issue is related to MAVENUPLOAD-1879 > Thanks in advance. -- 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-576) Invalid digests for http://repo1.maven.org/maven2/biz/aQute/bndlib/0.0.238/bndlib-0.0.238.pom
[ http://jira.codehaus.org/browse/MEV-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-576. -- Assignee: Carlos Sanchez Resolution: Fixed Redeployed pom in binary mode > Invalid digests for > http://repo1.maven.org/maven2/biz/aQute/bndlib/0.0.238/bndlib-0.0.238.pom > - > > Key: MEV-576 > URL: http://jira.codehaus.org/browse/MEV-576 > Project: Maven Evangelism > Issue Type: Bug >Reporter: SebbASF >Assignee: Carlos Sanchez > > The SHA1 and MD5 digests for > http://repo1.maven.org/maven2/biz/aQute/bndlib/0.0.238/bndlib-0.0.238.pom > don't agree with the file contents -- 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-572) http://repo1.maven.org/maven/batik/jars/ has bad MD5 entry
[ http://jira.codehaus.org/browse/MEV-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124418 ] Carlos Sanchez commented on MEV-572: it's due to the rewrite rules here https://svn.apache.org/repos/asf/maven/archiva/tools/trunk/maven-meeper/src/bin/synchronize/m1-m2-mod-rewrite-rules.txt > http://repo1.maven.org/maven/batik/jars/ has bad MD5 entry > -- > > Key: MEV-572 > URL: http://jira.codehaus.org/browse/MEV-572 > Project: Maven Evangelism > Issue Type: Bug >Reporter: SebbASF > > The directory of http://repo1.maven.org/maven/batik/jars/ looks like this to > me: > ... > batik-1.5-fop-0.20-5.jar 22-Jan-2004 08:37 2.0M > batik-1.5-fop-0.20-5.jar.md5 22-Jan-2004 08:37 33 > ... > However, when the md5 is downloaded, it is exactly the same as the jar > - i.e. not the 33 bytes of hash+EOL expected. > Looks like there is a bad link or perhaps a bad htaccess file which is > causing the wrong file to be downloaded. > The equivalent ibiblio entry seems OK: > http://mirrors.ibiblio.org/pub/mirrors/maven/batik/jars/ -- 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-1924) Sync com.exadel.flamingo repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1924. --- Assignee: Carlos Sanchez Resolution: Fixed > Sync com.exadel.flamingo repository > --- > > Key: MAVENUPLOAD-1924 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1924 > Project: maven-upload-requests > Issue Type: Task >Reporter: Artem Pleskatsevich >Assignee: Carlos Sanchez > Attachments: com.exadel.flamingo.sh > > > Would like to synchronize the repository at > http://repository.exadel.com/com/exadel/flamingo/ with the central maven > repository. Access allowed from beaver.codehaus.org only. -- 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: (SUREFIRE-459) Integration test using Jetty and JSP 2.1 fails after update to maven-surefire-plugin 2.4
[ http://jira.codehaus.org/browse/SUREFIRE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124423 ] Dan Fabulich commented on SUREFIRE-459: --- Rather than just grabbing the current latest (which might be broken for some other reason), could you give me a specific SVN URL and revision number to pull down? Prior to knowing anything else about your failing test, I might suggest that you take a look at SUREFIRE-453 and try configuring 2.4 with useSystemClassLoader=false. > Integration test using Jetty and JSP 2.1 fails after update to > maven-surefire-plugin 2.4 > > > Key: SUREFIRE-459 > URL: http://jira.codehaus.org/browse/SUREFIRE-459 > Project: Maven Surefire > Issue Type: Bug > Components: classloading, plugin >Affects Versions: 2.4, 2.4.1 > Environment: Maven 2.0.8, Windows XP >Reporter: Nils-Helge Garli > > We have an integration test running in a Struts 2 sample application, and > after the maven-surefire-plugin was updated from 2.3 to 2.4, the test is > failing. There's an issue registered in the Struts 2 JIRA explaining the > error: https://issues.apache.org/struts/browse/WW-2494 > I have no idea what's causing the error, but I suspect it has something to do > witn classloader configuration, as aparently no tld files are found inside > the jar files on the classpath. > It should be pretty easy to reproduce. Just checkout the Struts 2 code and > run 'mvn test' on the portlet example application. -- 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-1915) Upload ZK Forge Libraries to the central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1915. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload ZK Forge Libraries to the central repository > --- > > Key: MAVENUPLOAD-1915 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1915 > Project: maven-upload-requests > Issue Type: Task >Reporter: Tom M. Yeh >Assignee: Carlos Sanchez > > http://www.zkoss.org/maven/bundles/zkforge/fckez-2.5.1_1-bundle.jar > http://www.zkoss.org > http://sourceforge.net/users/tomyeh/ > ZK Forge is a collection of libraries for the ZK project. > ZK is an open-source Ajax Web framework that enables rich user interface for > Web applications with no JavaScript and little programming. -- 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-1914) upload xSocket V2.0-alpha-2 & http, multiplexed
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1914. --- Assignee: Carlos Sanchez Resolution: Fixed > upload xSocket V2.0-alpha-2 & http, multiplexed > --- > > Key: MAVENUPLOAD-1914 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1914 > Project: maven-upload-requests > Issue Type: Wish >Reporter: greg >Assignee: Carlos Sanchez > > please upload all 3 bundles. > Thanks -- 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-1917) Upload beans binding 1.2.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124424 ] Carlos Sanchez commented on MAVENUPLOAD-1917: - groupId must be net.java.dev.beansbinding > Upload beans binding 1.2.1 > -- > > Key: MAVENUPLOAD-1917 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1917 > Project: maven-upload-requests > Issue Type: Task >Reporter: Steve Taylor > Attachments: beansbinding-1.2.1-bundle.jar > > > The bundle isn't publicly accessable, but it's attached here. Hope that's ok. -- 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-1879) Synchronize loom repository with central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1879. --- Assignee: Carlos Sanchez Resolution: Fixed > Synchronize loom repository with central > > > Key: MAVENUPLOAD-1879 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1879 > Project: maven-upload-requests > Issue Type: Task >Reporter: Ignacio Coloma >Assignee: Carlos Sanchez > Attachments: org.extrema-sistemas.loom.sh, org.extrema.loom.sh > > > As indicated in the maven instructions, we have created a repository under > http://loom.sourceforge.net/repository > We would like to synchronize with central. You can find the script attached. -- 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-1916) jwebunit 1.4.1 into central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1916. --- Assignee: Carlos Sanchez Resolution: Incomplete please read the instructions http://maven.apache.org/guides/mini/guide-central-repository-upload.html > jwebunit 1.4.1 into central > --- > > Key: MAVENUPLOAD-1916 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1916 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Inge Johnsen >Assignee: Carlos Sanchez > > test framework -- 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-1938) Upload Annsor to the Maven Central Repository.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1938. --- Assignee: Carlos Sanchez Resolution: Fixed next time you'll have to use a sychronized repo if you use parent poms > Upload Annsor to the Maven Central Repository. > -- > > Key: MAVENUPLOAD-1938 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1938 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Richard Burton >Assignee: Carlos Sanchez > Attachments: annsor-core-1.0.3-bundle.jar, > annsor-core-1.0.3-sources.jar, annsor-core-1.0.3.jar, pom.xml > > > Annsor is a lightweight runtime annotation processor. The purpose of Annsor > is to simplify processing of Annotations during runtime, without sacrificing > performance or affecting your API. > Thank you, > Richard L. Burton III -- 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-1918) Upload ZK Forge Libraries to the central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1918. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload ZK Forge Libraries to the central repository > --- > > Key: MAVENUPLOAD-1918 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1918 > Project: maven-upload-requests > Issue Type: Task >Reporter: Henri Chen >Assignee: Carlos Sanchez > > http://www.zkoss.org/maven/bundles/zkforge/gmapsz-2.0_7-bundle.jar > http://www.zkoss.org > http://sourceforge.net/users/henrichen/ -- 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-1921) Upload ZK 3.0.3 to the central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1921. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload ZK 3.0.3 to the central repository > - > > Key: MAVENUPLOAD-1921 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1921 > Project: maven-upload-requests > Issue Type: Task >Reporter: Tom M. Yeh >Assignee: Carlos Sanchez > > http://www.zkoss.org/maven/bundles/3.0.3/zcommon-3.0.3-bundle.jar > http://www.zkoss.org/maven/bundles/3.0.3/zweb-3.0.3-bundle.jar > http://www.zkoss.org/maven/bundles/3.0.3/zk-3.0.3-bundle.jar > http://www.zkoss.org/maven/bundles/3.0.3/zul-3.0.3-bundle.jar > http://www.zkoss.org/maven/bundles/3.0.3/zhtml-3.0.3-bundle.jar > http://www.zkoss.org/maven/bundles/3.0.3/zml-3.0.3-bundle.jar > http://www.zkoss.org/maven/bundles/3.0.3/zkex-3.0.3-bundle.jar > http://www.zkoss.org/maven/bundles/3.0.3/zkmax-3.0.3-bundle.jar > http://www.zkoss.org/maven/bundles/3.0.3/zkplus-3.0.3-bundle.jar > http://www.zkoss.org > http://sourceforge.net/users/tomyeh/ > ZK is an open-source Ajax Web framework that enables rich user interface for > Web applications with no JavaScript and little programming. > Thanks. -- 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-1908) JavaCSV 2.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1908. --- Resolution: Fixed > JavaCSV 2.0 > --- > > Key: MAVENUPLOAD-1908 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1908 > Project: maven-upload-requests > Issue Type: Task >Reporter: Grzegorz Slowikowski >Assignee: Carlos Sanchez > Attachments: javacsv-2.0-bundle.jar > > > Java CSV is a small fast open source java library for reading and writing CSV > and plain delimited text files. All kinds of CSV files can be handled, text > qualified, Excel formatted, etc. > This is the first upload of this 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-1936) Hibernate 3.2.6 ga upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1936. --- Assignee: Carlos Sanchez Resolution: Incomplete see instructions http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Hibernate 3.2.6 ga upload > - > > Key: MAVENUPLOAD-1936 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1936 > Project: maven-upload-requests > Issue Type: Task >Reporter: Emil A. Lefkof III >Assignee: Carlos Sanchez > > Not a member of the Hibernate team but thought the new 3.2.6 ga should be > uploaded to ibiblio -- 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-1931) Please update strutstestcase to version 2.1.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124429 ] Carlos Sanchez commented on MAVENUPLOAD-1931: - you need to provide a jar with sources jar, binary jar and pom inside. See instructions http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Please update strutstestcase to version 2.1.4 > - > > Key: MAVENUPLOAD-1931 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1931 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Yuriy Tumakha > Attachments: strutstestcase-2.1.4-1.2-2.4-sources.jar, > strutstestcase-2.1.4-1.2-2.4.pom, strutstestcase-2.1.4.jar > > > Download strutstestcase 2.1.4 > http://sourceforge.net/project/showfiles.php?group_id=39190 > 1. From > http://downloads.sourceforge.net/strutstestcase/strutstest214-1.2_2.4.zip?modtime=1192154035&big_mirror=0 > extract "strutstest\strutstest-2.1.4.jar" and rename as > "strutstestcase-2.1.4.jar" > 2. Download > http://downloads.sourceforge.net/strutstestcase/strutstest-214-src.zip?modtime=1192154061&big_mirror=0 > and repack as "strutstestcase-2.1.4-1.2-2.4-sources.jar" > 3. strutstestcase-2.1.4-1.2-2.4.pom - in attachment. -- 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: (SUREFIRE-459) Integration test using Jetty and JSP 2.1 fails after update to maven-surefire-plugin 2.4
[ http://jira.codehaus.org/browse/SUREFIRE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124433 ] Nils-Helge Garli commented on SUREFIRE-459: --- Sorry for not beeing more specific. Anyway, it appears that this has been resolved in the 2.4.2-SNAPSHOT. I will re-test it when 2.4.2 is released to make sure it's still ok. > Integration test using Jetty and JSP 2.1 fails after update to > maven-surefire-plugin 2.4 > > > Key: SUREFIRE-459 > URL: http://jira.codehaus.org/browse/SUREFIRE-459 > Project: Maven Surefire > Issue Type: Bug > Components: classloading, plugin >Affects Versions: 2.4, 2.4.1 > Environment: Maven 2.0.8, Windows XP >Reporter: Nils-Helge Garli > > We have an integration test running in a Struts 2 sample application, and > after the maven-surefire-plugin was updated from 2.3 to 2.4, the test is > failing. There's an issue registered in the Struts 2 JIRA explaining the > error: https://issues.apache.org/struts/browse/WW-2494 > I have no idea what's causing the error, but I suspect it has something to do > witn classloader configuration, as aparently no tld files are found inside > the jar files on the classpath. > It should be pretty easy to reproduce. Just checkout the Struts 2 code and > run 'mvn test' on the portlet example application. -- 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-1913) backport-util-concurrent for Java 1.2 and 1.3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1913. --- Assignee: Carlos Sanchez Resolution: Fixed manual uploads take long time, you can provide an automatic sync, see http://maven.apache.org/guides/mini/guide-central-repository-upload.html > backport-util-concurrent for Java 1.2 and 1.3 > - > > Key: MAVENUPLOAD-1913 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1913 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Taras Puchko >Assignee: Carlos Sanchez > > http://tarasp.fileave.com/maven2/backport-util-concurrent-java12-3.1-bundle.jar > http://backport-jsr166.sourceforge.net/ > This package is the backport of java.util.concurrent API, introduced in Java > 5.0, to Java 1.2 and 1.3. -- 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-1905) Upload request for artifact: Java Utilities - OstermillerUtils
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1905. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload request for artifact: Java Utilities - OstermillerUtils > -- > > Key: MAVENUPLOAD-1905 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1905 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Diego Schivo >Assignee: Carlos Sanchez > > http://repository.openmindonline.it/_bundle-upload/ostermiller-utils-1.07.00.jar > http://ostermiller.org/utils > I'm not a developer, please upload. -- 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-1902) sync central repo with mmm releases repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1902. --- Assignee: Carlos Sanchez Resolution: Fixed > sync central repo with mmm releases repository > -- > > Key: MAVENUPLOAD-1902 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1902 > Project: maven-upload-requests > Issue Type: Task >Reporter: Jörg Hohwiller >Assignee: Carlos Sanchez > Attachments: net.sf.mmm.sh > > > I am the admin and maintainer of the mmm project: > http://m-m-m.sourceforge.net/maven/index.html > We provide cool open-source software licensed under ASL. > Maven2 is our project-management-tool. > We would like to have our releases available in the central maven repository. > Therefore we read and followed the instructions we found here: > http://maven.apache.org/guides/mini/guide-central-repository-upload.html > You will find a sync-script 'net.sf.mmm.sh' attached. > I hope everything is perfect. Please let us know, if we did something wrong. -- 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-1929) Upload FreeMarker 2.3.12
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1929. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload FreeMarker 2.3.12 > > > Key: MAVENUPLOAD-1929 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1929 > Project: maven-upload-requests > Issue Type: Task >Reporter: Mirko Nasato >Assignee: Carlos Sanchez > -- 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-1922) JSTags is a Java Open Source Tags Library whose aim is to provide a set of easy-to-use tags which perform JavaScript related tasks.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124428 ] Carlos Sanchez commented on MAVENUPLOAD-1922: - file names dont match artifactId and version > JSTags is a Java Open Source Tags Library whose aim is to provide a set of > easy-to-use tags which perform JavaScript related tasks. > --- > > Key: MAVENUPLOAD-1922 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1922 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Soraya Sanchez > > http://jstags.sourceforge.net/bundles/jstags-lib-1.1-bundle.jar > http://jstags.sourceforge.net > http://jstags.sourceforge.net/team-list.html > JSTags is a Java Open Source Tags Library whose aim is to provide a set of > easy-to-use tags which perform common tasks that, otherwise, would have to be > implemented by means of JavaScript code. By using JSTags, it is as simple as > including a tag instead of having to create JavaScript code yourself...you > just forget about that part. > Please, upload this. > Thanks! -- 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-1932) Update j2ssh-common and j2ssh-core
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1932. --- Assignee: Carlos Sanchez Resolution: Incomplete please read instructions http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Update j2ssh-common and j2ssh-core > -- > > Key: MAVENUPLOAD-1932 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1932 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Henri Dupre >Assignee: Carlos Sanchez > Attachments: sshtools-0.2.9.zip > > -- 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: (SUREFIRE-459) Integration test using Jetty and JSP 2.1 fails after update to maven-surefire-plugin 2.4
[ http://jira.codehaus.org/browse/SUREFIRE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-459. - Resolution: Fixed Marking Fixed > Integration test using Jetty and JSP 2.1 fails after update to > maven-surefire-plugin 2.4 > > > Key: SUREFIRE-459 > URL: http://jira.codehaus.org/browse/SUREFIRE-459 > Project: Maven Surefire > Issue Type: Bug > Components: classloading, plugin >Affects Versions: 2.4, 2.4.1 > Environment: Maven 2.0.8, Windows XP >Reporter: Nils-Helge Garli > > We have an integration test running in a Struts 2 sample application, and > after the maven-surefire-plugin was updated from 2.3 to 2.4, the test is > failing. There's an issue registered in the Struts 2 JIRA explaining the > error: https://issues.apache.org/struts/browse/WW-2494 > I have no idea what's causing the error, but I suspect it has something to do > witn classloader configuration, as aparently no tld files are found inside > the jar files on the classpath. > It should be pretty easy to reproduce. Just checkout the Struts 2 code and > run 'mvn test' on the portlet example application. -- 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-1919) Please upload Retrotranslator 1.2.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1919. --- Assignee: Carlos Sanchez Resolution: Fixed > Please upload Retrotranslator 1.2.4 > --- > > Key: MAVENUPLOAD-1919 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1919 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Taras Puchko >Assignee: Carlos Sanchez > > http://tarasp.fileave.com/maven2/retrotranslator-runtime-1.2.4-bundle.jar > http://tarasp.fileave.com/maven2/retrotranslator-runtime13-1.2.4-bundle.jar > http://tarasp.fileave.com/maven2/retrotranslator-transformer-1.2.4-bundle.jar > http://retrotranslator.sourceforge.net/ > http://sourceforge.net/users/tarasp/ > This upload depends on MAVENUPLOAD-1913 -- 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: (MECLIPSE-391) An error occurred while automatically activating bundle org.maven.ide.eclipse (465).
An error occurred while automatically activating bundle org.maven.ide.eclipse (465). Key: MECLIPSE-391 URL: http://jira.codehaus.org/browse/MECLIPSE-391 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: M2Eclipse support Affects Versions: 2.0 Environment: Windows XP, installed java 1.6, installed eclipse 3.3.1.1 Reporter: Shubhangi Sharad Wakodikar An error occurred while automatically activating bundle org.maven.ide.eclipse (465). Above is the error log I am getting after installing eclipse plugin for maven2 ie Maven Integration for Eclipse IDE. What could be the problem? Because of this error, it is not able to create settings.xml file in /.m2/ Hence it gives me error of file not found at specified location. Please help. Thanks in advance -- 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
