[jira] Closed: (MAVENUPLOAD-2779) Please remove synchronisation for projects EasyMock and Objenesis
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juven Xu closed MAVENUPLOAD-2779. - Resolution: Fixed was already fixed, see http://mail-archives.apache.org/mod_mbox/maven-repo-maintainers/201009.mbox/%3caanlktinpayma1xkrpi1r67qke5hr8kpxd3cqhaua7...@mail.gmail.com%3e > Please remove synchronisation for projects EasyMock and Objenesis > - > > Key: MAVENUPLOAD-2779 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2779 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Henri Tremblay >Assignee: Juven Xu > > Both are synchronized from the EasyMock repository at this address > http://www.easymock.org/maven/repository/ > They will now be uploaded to Sonatype repository. > URLs: > http://www.easymock.org > http://www.objenesis.org > Contributor: > http://www.easymock.org > http://objenesis.googlecode.com/svn/docs/acknowledgements.html -- 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-2799) please upload maven-precheck-plugin to the maven repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239564#action_239564 ] Jaehyeon Nam commented on MAVENUPLOAD-2799: --- Thanks for your comment. :) > please upload maven-precheck-plugin to the maven repository > --- > > Key: MAVENUPLOAD-2799 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2799 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Jaehyeon Nam > Attachments: maven-precheck-plugin-1.0-bundle.jar > > > http://maven-precheck-plugin.googlecode.com/files/maven-precheck-plugin-1.0-bundle.jar > > http://code.google.com/p/maven-precheck-plugin > http://code.google.com/p/maven-precheck-plugin/people/list > I'm a developer in "maven-precheck-plugin", and want to use the > "org.openwebtop.maven.plugins" groupId. > I own "openwebtop.org" domain, you can see my email > address(dotol...@gmail.com) in > http://reports.internic.net/cgi/whois?whois_nic=openwebtop.org&type=domain -- 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: (MSITE-514) Document / Content Harvesting (Word, Excel.. others)
Document / Content Harvesting (Word, Excel.. others)
Key: MSITE-514
URL: http://jira.codehaus.org/browse/MSITE-514
Project: Maven 2.x Site Plugin
Issue Type: New Feature
Affects Versions: 3.0-beta-2
Reporter: Andrew Hughes
Hi Guys,
Have an idea, but I wouldn't know where to get started on this... besides I
think this is more than a one person job. Just like we have reporting plugins
and the project-info reports, I think a "project documents" site plugin would
be an excellent idea.
Purpose:
The primary purpose is to provide easy integration of non apt, xdoc...
formatted documents into maven sites.
Objectives:
The primary objective should be to create a menu on the site that lists all of
the discovered documents in the project source.
Example (that extents the normal "Project Documentation" menu.
* Project Documentation
** Project Information
*** Continuous Integration
*** Issue Tracking
*** Project Team
*** Source Repository
** Project Reports
*** Maven Surefire Report
*** Other Report
** Documents <- NEW name TDB, clicking on this should open a page with a
table of all documents with their harvested metadata.
*** Acme Project SRS (doc) <- New, showing a harvested word document.. the link
title is the document title
*** Contract (pdf) <- New, showing a harvested pdf document.
*** Estimates (xls) <- New, an excel spreadsheet
*** Risk Register (xls) <- New, another excel spreadsheet.
The index page's could hopefully gather enuff metadata about the documents to
create something that looks like...
||Title||Filename||Format||Author||Last Modified||Last Mofified By||
|Acme Project SRS| APD-ACME-SRS.doc|doc|John Smith|14-10-2010|A Hughes|
|Contact| APC-ACME-CONTACT-23489345.pdf|pdf|N/A|22-02-2010|N/A|
|Estimates| APE-ACME-Estimates.xls|xls|A Schwarzenegger|22-02-2010|JP Freely|
Implementation:
I got very little idea how this kinda thing could be integrated into the site.
From menu creation, velocity templates e.t.c... sorry I am quite useless. I do
know that we have things like http://poi.apache.org/ to help gather meta data
about microsoft documents, and similarly pdf is available. LaTex or other
formats hopefully have similar API's.
Configuration:
I'd think that the pom config might help define how this could work.. what
options and functionality it would/could potentially offer...
{noformat}
...ommitting normal stuff...
${basedir}/documents
**.doc
**.xls
Documentz
title,version,author,lastModifiedBy,lastModifiedData
{noformat}
What do you think, is this a practical idea? is this achievable and how much
work would be involved?
CHEERS :)
--
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-4864) npe when transferring artifacts
[
http://jira.codehaus.org/browse/MNG-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239497#action_239497
]
Benjamin Bentmann commented on MNG-4864:
The code in question:
{noformat}
for ( Map.Entry entry : downloads.entrySet() )
{
long total = entry.getKey().getContentLength();
long complete = entry.getValue().longValue(); // line 60
{noformat}
which suggests {{entry.getValue()}} is {{null}} which is interesting given that
we iterate a {{ConcurrentHashMap}} here which doesn't allow {{null}} values.
What JRE version/vendor are you using?
> npe when transferring artifacts
> ---
>
> Key: MNG-4864
> URL: http://jira.codehaus.org/browse/MNG-4864
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0
>Reporter: jgon2
>
> I get the following NPE when running a mvn clean install with an empty local
> repository. The two stracktraces below show that the build breaks with
> different artifacts but always at the same place.
> If I relaunch the build several times, it finally succeeds.
> {code}
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.cli.ConsoleMavenTransferListener.transferProgressed(ConsoleMavenTransferListener.java:60)
>
> [ERROR] Failed to execute goal on project stdlib-core: Could not resolve
> dependencies for project com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could
> not transfer artifact org.apache.maven:maven-repository-metadata:jar:2.0.8
> from nexus (http://maven/nexus/content/groups/public): NullPointerException
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project stdlib-core: Could not resolve dependencies for project
> com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could not transfer artifact
> org.apache.maven:maven-repository-metadata:jar:2.0.8 from nexus
> (http://maven/nexus/content/groups/public): NullPointerException
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:190)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:104)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:244)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:187)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:314)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.project.DependencyResolutionException: Could not
> resolve dependencies for project
> com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could not transfer artifact
> org.apache.maven:maven-repository-metadata:jar:2.0.8 from nexus
> (http://maven/nexus/content/groups/public): NullPointerException
> at
> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:156)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:165)
>
> ... 22 more
> Caused by:
[jira] Created: (MNG-4864) npe when transferring artifacts
npe when transferring artifacts
---
Key: MNG-4864
URL: http://jira.codehaus.org/browse/MNG-4864
Project: Maven 2 & 3
Issue Type: Bug
Affects Versions: 3.0
Reporter: jgon2
I get the following NPE when running a mvn clean install with an empty local
repository. The two stracktraces below show that the build breaks with
different artifacts but always at the same place.
If I relaunch the build several times, it finally succeeds.
{code}
Caused by: java.lang.NullPointerException
at
org.apache.maven.cli.ConsoleMavenTransferListener.transferProgressed(ConsoleMavenTransferListener.java:60)
[ERROR] Failed to execute goal on project stdlib-core: Could not resolve
dependencies for project com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could
not transfer artifact org.apache.maven:maven-repository-metadata:jar:2.0.8 from
nexus (http://maven/nexus/content/groups/public): NullPointerException -> [Help
1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
on project stdlib-core: Could not resolve dependencies for project
com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could not transfer artifact
org.apache.maven:maven-repository-metadata:jar:2.0.8 from nexus
(http://maven/nexus/content/groups/public): NullPointerException
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:190)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:104)
at
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:244)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:187)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:314)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.project.DependencyResolutionException: Could not
resolve dependencies for project com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT:
Could not transfer artifact
org.apache.maven:maven-repository-metadata:jar:2.0.8 from nexus
(http://maven/nexus/content/groups/public): NullPointerException
at
org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:156)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:165)
... 22 more
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Could
not transfer artifact org.apache.maven:maven-repository-metadata:jar:2.0.8 from
nexus (http://maven/nexus/content/groups/public): NullPointerException
at
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:488)
at
org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveArtifacts(DefaultRepositorySystem.java:258)
at
org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:288)
at
org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:150)
... 23 more
Caused by: org.sonatype.aether.transfer.ArtifactTransferException: Could not
transfer artifact o
[jira] Commented: (MAVENUPLOAD-2789) OSGi 4.2.0 Enterprise API
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239491#action_239491 ] David Bosschaert commented on MAVENUPLOAD-2789: --- BTW the OSGi 4.2.0 Enterprise API jar is now available at http://repo1.maven.org/maven2/org/osgi/org.osgi.enterprise/4.2.0/ > OSGi 4.2.0 Enterprise API > - > > Key: MAVENUPLOAD-2789 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2789 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Thomas Diesler > Attachments: org.osgi.enterprise-4.2.0.jar, osgi.enterprise.jar > > > This is the recently released OSGi 4.2.0 Enterprise API in bundle form. I > have manually created sha1 checksums for all artifacts; the pom is > maven-generated. -- 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: (MNG-4863) Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute. Getting ClasCastException.
[ http://jira.codehaus.org/browse/MNG-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4863. -- Resolution: Won't Fix Assignee: Benjamin Bentmann > Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute. > Getting ClasCastException. > -- > > Key: MNG-4863 > URL: http://jira.codehaus.org/browse/MNG-4863 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 3.0 > Environment: Windows XP, Jdk 1.6.0_20 >Reporter: Bodhayan Chakraborty >Assignee: Benjamin Bentmann > > Hi, > I am getting the below error after I upgrade Maven 2.2.1 to Maven 3.0. > ... > [ERROR] Failed to execute goal > org.codehaus.groovy.maven:gmaven-plugin:1.0:execute (set-bastion-credentials) > on project esb-parent-pom: java.lang.ClassCastException: script1286984516651 > cannot be cast to groovy.lang.GroovyObject -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > ... > This is the plugin that I am using. > > org.codehaus.groovy.maven > gmaven-plugin > > > > But if I change the plugin like below, it is working. > > org.codehaus.gmaven > gmaven-plugin > 1.3 > > > > Is it mandatory to change the Gmaven plugin if I upgrade from maven 2.2.1 to > 3.0? > Please let me know, > Thanks, > Bodhayan. -- 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-2777) Version 2.3-jdk16 of UISpec4J
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2777. -- Resolution: Won't Fix This form of bundle upload isn't supported anymore. See the documentation here for how you can self-serve and get the artifacts into central within a day: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Version 2.3-jdk16 of UISpec4J > - > > Key: MAVENUPLOAD-2777 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2777 > Project: Maven Upload Requests > Issue Type: New Feature >Reporter: Pascal Pratmarty > > UISpec4J is an Open Source functional and/or unit testing library for > Swing-based Java applications, built on top of the JUnit and TestNG test > harnesses. -- 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-2776) Version 2.3-jdk15 of UISpec4J
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2776. -- Resolution: Won't Fix This form of bundle upload isn't supported anymore. See the documentation here for how you can self-serve and get the artifacts into central within a day: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Version 2.3-jdk15 of UISpec4J > - > > Key: MAVENUPLOAD-2776 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2776 > Project: Maven Upload Requests > Issue Type: New Feature >Reporter: Pascal Pratmarty > > UISpec4J is an Open Source functional and/or unit testing library for > Swing-based Java applications, built on top of the JUnit and TestNG test > harnesses. -- 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-2773) Upload jTDS 1.2.5
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2773. -- Resolution: Won't Fix > Upload jTDS 1.2.5 > - > > Key: MAVENUPLOAD-2773 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2773 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Holger Rehn >Assignee: Juven Xu > > I'm a jTDS developer (at sourceforge I'm registered under the pseudonym > "ickzon"). > http://sourceforge.net/projects/jtds/ -- 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-2774) I am DynamicJasper's project leader, please upload.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2774. -- Resolution: Won't Fix > I am DynamicJasper's project leader, please upload. > --- > > Key: MAVENUPLOAD-2774 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2774 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Juan Manuel Alvarez >Assignee: Juven Xu > > DynamicJasper (DJ) is an API that hides the complexity of Jasper Reports, it > helps developers to save time when designing simple/medium complexity reports > generating the layout of the report elements automatically. It creates > reports dynamically, defining at runtime the columns, column width (auto > width), groups, variables, fonts, charts, crosstabs, sub reports (that can > also be dynamic), page size and everything else that you can define at design > time. -- 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-2805) jt400-7.1-bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2805. -- Resolution: Won't Fix This form of bundle upload isn't supported anymore. See the documentation here for how you can self-serve and get the artifacts into central within a day: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > jt400-7.1-bundle > > > Key: MAVENUPLOAD-2805 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2805 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Jeff Lee > Attachments: jt400-7.1-bundle.jar, jt400-7.1-javadoc-bundle.jar, > jt400-7.1-source-bundle.jar > > > https://sourceforge.net/projects/jt400 > http://jt400.sourceforge.net/ > http://jt400.sourceforge.net/team.html > The IBM Toolbox for Java is a library of Java classes supporting the > client/server and internet programming models to a system running OS/400 or > i5/OS. The classes can be used by Java applets, servlets, and applications to > easily access OS/400 and i5/OS data and resources. -- 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-2789) OSGi 4.2.0 Enterprise API
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2789. -- Resolution: Won't Fix This form of bundle upload isn't supported anymore. See the documentation here for how you can self-serve and get the artifacts into central within a day: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > OSGi 4.2.0 Enterprise API > - > > Key: MAVENUPLOAD-2789 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2789 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Thomas Diesler > Attachments: org.osgi.enterprise-4.2.0.jar, osgi.enterprise.jar > > > This is the recently released OSGi 4.2.0 Enterprise API in bundle form. I > have manually created sha1 checksums for all artifacts; the pom is > maven-generated. -- 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-2778) upload request for jaxb ri 2.1.13, jaxb-api 2.2.1 and jaxb ri 2.2.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2778. -- Resolution: Won't Fix This form of bundle upload isn't supported anymore. See the documentation here for how you can self-serve and get the artifacts into central within a day: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > upload request for jaxb ri 2.1.13, jaxb-api 2.2.1 and jaxb ri 2.2.1 > --- > > Key: MAVENUPLOAD-2778 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2778 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Pavel Bucek > > Hello, > can you please upload following artifacts to maven central? > https://jaxb.dev.java.net/2.1.13/bundles2mavenCentral-signed/jaxb-impl-2.1.13-bundle.jar > https://jaxb.dev.java.net/2.1.13/bundles2mavenCentral-signed/jaxb1-impl-2.1.13-bundle.jar > https://jaxb.dev.java.net/2.1.13/bundles2mavenCentral-signed/jaxb-xjc-2.1.13-bundle.jar > https://jaxb.dev.java.net/2.2.1/bundles2mavenCentral-signed/jaxb-api-2.2.1-bundle.jar > https://jaxb.dev.java.net/2.2.1/bundles2mavenCentral-signed/jaxb-api-osgi-2.2.1-bundle.jar > https://jaxb.dev.java.net/2.2.1/bundles2mavenCentral-signed/jaxb-impl-2.2.1-bundle.jar > https://jaxb.dev.java.net/2.2.1/bundles2mavenCentral-signed/jaxb1-impl-2.2.1-bundle.jar > https://jaxb.dev.java.net/2.2.1/bundles2mavenCentral-signed/jaxb-xjc-2.2.1-bundle.jar > https://jaxb.dev.java.net/2.2.1/bundles2mavenCentral-signed/jaxb-osgi-2.2.1-bundle.jar > Thanks, > Pavel -- 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-2802) MarkdownPapers artifacts upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2802. -- Resolution: Won't Fix This form of bundle upload isn't supported anymore. See the documentation here for how you can self-serve and get the artifacts into central within a day: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > MarkdownPapers artifacts upload > --- > > Key: MAVENUPLOAD-2802 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2802 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Larry Ruiz > > http://github.com/downloads/lruiz/MarkdownPapers/markdownpapers-core-0.3.0-bundle.jar > http://github.com/downloads/lruiz/MarkdownPapers/markdownpapers-parent-0.3.0-bundle.jar > http://github.com/lruiz/MarkdownPapers > I am a developer in MarkdownPapers, 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-2800) New version of XINS for Maven2 repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2800. -- Resolution: Won't Fix This form of bundle upload isn't supported anymore. See the documentation here for how you can self-serve and get the artifacts into central within a day: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > New version of XINS for Maven2 repository > - > > Key: MAVENUPLOAD-2800 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2800 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Anthony Goubard > > Hi, > Here are new JAR file that I'd like to have uploaded in Maven: > http://www.xins.org/maven/xins-server-2.3.jar > http://www.xins.org/maven/xins-common-2.3.jar > http://www.xins.org/maven/xins-client-2.3.jar > http://www.xins.org/maven/logdoc-2.3.jar > Kind regards, > Anthony Goubard -- 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-2797) Java library which allows you to serialize classes with non serializable fields, like input streams. It's very useful when you are using input streams or blobs with E
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2797. -- Resolution: Won't Fix This form of bundle upload isn't supported anymore. See the documentation here for how you can self-serve and get the artifacts into central within a day: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Java library which allows you to serialize classes with non serializable > fields, like input streams. It's very useful when you are using input streams > or blobs with EJB > > > Key: MAVENUPLOAD-2797 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2797 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Yaroslav Klymko > > I'm 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-2801) Table - simple collection, allowing multiple custom fast searchable indexes.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2801. -- Resolution: Won't Fix This form of bundle upload isn't supported anymore. See the documentation here for how you can self-serve and get the artifacts into central within a day: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Table - simple collection, allowing multiple custom fast searchable > indexes. > --- > > Key: MAVENUPLOAD-2801 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2801 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Illarion Kovalchuk > Attachments: tablej-0.1.0-SNAPSHOT-bundle.jar > > > http://code.google.com/p/tablej/ > Could you please upload 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-2795) Please upload Nomin mapping engine
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2795. -- Resolution: Fixed > Please upload Nomin mapping engine > -- > > Key: MAVENUPLOAD-2795 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2795 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Dmitry Dobrynin > > https://sourceforge.net/projects/nomin/files/nomin-1.0.0-bundle.jar/download > http://nomin.sourceforge.net > http://nomin.sourceforge.net/team-list.html > I'm a developer in nomin, 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-2799) please upload maven-precheck-plugin to the maven repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2799. -- Resolution: Won't Fix This form of bundle upload isn't supported anymore. See the documentation here for how you can self-serve and get the artifacts into central within a day: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > please upload maven-precheck-plugin to the maven repository > --- > > Key: MAVENUPLOAD-2799 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2799 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Jaehyeon Nam > Attachments: maven-precheck-plugin-1.0-bundle.jar > > > http://maven-precheck-plugin.googlecode.com/files/maven-precheck-plugin-1.0-bundle.jar > > http://code.google.com/p/maven-precheck-plugin > http://code.google.com/p/maven-precheck-plugin/people/list > I'm a developer in "maven-precheck-plugin", and want to use the > "org.openwebtop.maven.plugins" groupId. > I own "openwebtop.org" domain, you can see my email > address(dotol...@gmail.com) in > http://reports.internic.net/cgi/whois?whois_nic=openwebtop.org&type=domain -- 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-2796) The RSA host key for brap.tornado.no has changed, please accept the new one
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2796. -- Resolution: Won't Fix The rsync upload isn't supported anymore. See the documentation here for how you can get your project into a forge: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > The RSA host key for brap.tornado.no has changed, please accept the new one > --- > > Key: MAVENUPLOAD-2796 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2796 > Project: Maven Upload Requests > Issue Type: Improvement >Reporter: Edvin Syse > > brap.tornado.no was moved to a new machine, with a new RSA host key. Please > accept this so sync can be restored. -- 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-2792) Upload JSend NSCA
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2792. -- Resolution: Won't Fix This form of bundle upload isn't supported anymore. See the documentation here for how you can self-serve and get the artifacts into central within a day: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Upload JSend NSCA > - > > Key: MAVENUPLOAD-2792 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2792 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Raj Patel > > http://jsendnsca.googlecode.com/files/jsendnsca-2.0.0-bundle.jar > http://code.google.com/p/jsendnsca/ > http://code.google.com/p/jsendnsca/people/list > Can you please upload to the central repo, > many thanks > Raj -- 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-2787) JdbcHelper 0.3.1 Upload Request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2787. -- Resolution: Won't Fix This form of bundle upload isn't supported anymore. See the documentation here for how you can self-serve and get the artifacts into central within a day: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > JdbcHelper 0.3.1 Upload Request > --- > > Key: MAVENUPLOAD-2787 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2787 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Erdinc YILMAZEL > Attachments: jdbc-helper-0.3.1-bundle.jar > > > Inspired by Spring Jdbctemplate and Commons Dbutils projects, JdbcHelper? is > a very small library for helping the developers code common jdbc operations. > JdbcHelper? is very lightweight. It is only ~70K and it has no external > dependencies. -- 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-2784) com.browseengine.bobo:bobo-browse 2.0.7
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2784. -- Resolution: Fixed This form of bundle upload isn't supported anymore. See the documentation here for how you can self-serve and get the artifacts into central within a day: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > com.browseengine.bobo:bobo-browse 2.0.7 > --- > > Key: MAVENUPLOAD-2784 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2784 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: fabrizio giustina > > bundle contains binary jar, sources and 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: (MAVENUPLOAD-2785) Please add project "JODRepors" to the central repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2785. -- Resolution: Won't Fix This form of bundle upload isn't supported anymore. See the documentation here for how you can self-serve and get the artifacts into central within a day: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Please add project "JODRepors" to the central repo > -- > > Key: MAVENUPLOAD-2785 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2785 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Terry Liang > > Document Page: http://jodreports.sourceforge.net/docs/ > Team-list: > http://jodreports.sourceforge.net/docs/team-list.html > http://sourceforge.net/projects/jodreports/develop > Pom: > http://jodreports.svn.sourceforge.net/viewvc/jodreports/trunk/jodreports/pom.xml?view=markup > http://sourceforge.net/projects/jodreports/files/JODReports%202.2/2.2.1/jodreports-2.2.1.pom/download > Jar: > http://sourceforge.net/projects/jodreports/files/JODReports%202.2/2.2.1/jodreports-2.2.1.jar/download > I'm a developer and project admin in JODReports, 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-2786) ICOReader 1.04
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2786. -- Resolution: Won't Fix This form of bundle upload isn't supported anymore. See the documentation here for how you can self-serve and get the artifacts into central within a day: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > ICOReader 1.04 > -- > > Key: MAVENUPLOAD-2786 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2786 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: fabrizio giustina > -- 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-2782) Please upload objectify-led 1.1.0 to Maven repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2782. -- Resolution: Won't Fix This form of bundle upload isn't supported anymore. See the documentation here for how you can self-serve and get the artifacts into central within a day: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Please upload objectify-led 1.1.0 to Maven repository > - > > Key: MAVENUPLOAD-2782 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2782 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Steve Chaloner > > I'm a developer in objectify, and want to use the be.objectify groupId - you > can find my details at http://www.objectify.be/objectify-led/team-list.html > Thanks! > - Steve -- 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-2780) I am DynamicJasper's project leader, please upload.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2780. -- Resolution: Won't Fix This form of bundle upload isn't supported anymore. See the documentation here for how you can self-serve and get the artifacts into central within a day: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > I am DynamicJasper's project leader, please upload. > --- > > Key: MAVENUPLOAD-2780 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2780 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Juan Manuel Alvarez > > I am DynamicJasper's project leader, please upload. > DynamicJasper (DJ) is an API that hides the complexity of Jasper Reports, it > helps developers to save time when designing simple/medium complexity reports > generating the layout of the report elements automatically. It creates > reports dynamically, defining at runtime the columns, column width (auto > width), groups, variables, fonts, charts, crosstabs, sub reports (that can > also be dynamic), page size and everything else that you can define at design > time. > -- 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-2781) jt400-7.0-bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2781. -- Resolution: Fixed This form of bundle upload isn't supported anymore. See the documentation here for how you can self-serve and get the artifacts into central within a day: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > jt400-7.0-bundle > > > Key: MAVENUPLOAD-2781 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2781 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Jeff Lee > Attachments: javadoc-7.0.zip, jt400-7.0-bundle.jar, jt400-7.0.jar > > > The IBM Toolbox for Java (also known as JTOpen) is a library of Java classes > supporting the client/server and internet programming models to a system > running OS/400, i5/OS, or IBM i. The classes can be used by Java applets, > servlets, and applications to easily access OS/400, i5/OS, and IBM i data and > resources. -- 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-4863) Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute. Getting ClasCastException.
[ http://jira.codehaus.org/browse/MNG-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239456#action_239456 ] Olivier Lamy commented on MNG-4863: --- yes it's mandatory :-) > Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute. > Getting ClasCastException. > -- > > Key: MNG-4863 > URL: http://jira.codehaus.org/browse/MNG-4863 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 3.0 > Environment: Windows XP, Jdk 1.6.0_20 >Reporter: Bodhayan Chakraborty > > Hi, > I am getting the below error after I upgrade Maven 2.2.1 to Maven 3.0. > ... > [ERROR] Failed to execute goal > org.codehaus.groovy.maven:gmaven-plugin:1.0:execute (set-bastion-credentials) > on project esb-parent-pom: java.lang.ClassCastException: script1286984516651 > cannot be cast to groovy.lang.GroovyObject -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > ... > This is the plugin that I am using. > > org.codehaus.groovy.maven > gmaven-plugin > > > > But if I change the plugin like below, it is working. > > org.codehaus.gmaven > gmaven-plugin > 1.3 > > > > Is it mandatory to change the Gmaven plugin if I upgrade from maven 2.2.1 to > 3.0? > Please let me know, > Thanks, > Bodhayan. -- 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-2804) Sync org.patterntesting repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2804. -- Resolution: Won't Fix As the project description says, the rsyncs are no longer supported. You can see here for information about how to get stuff into central: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Sync org.patterntesting repository > -- > > Key: MAVENUPLOAD-2804 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2804 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Oliver Boehm > Attachments: org.patterntesting.sh > > > Please synchronize http://patterntesting.sourceforge.net/m2/repository/ to > the central maven repository. > (http://jira.codehaus.org/browse/MAVENUPLOAD-1911 is obsolete now) -- 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-4863) Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute. Getting ClasCastException.
Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute. Getting ClasCastException. -- Key: MNG-4863 URL: http://jira.codehaus.org/browse/MNG-4863 Project: Maven 2 & 3 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 3.0 Environment: Windows XP, Jdk 1.6.0_20 Reporter: Bodhayan Chakraborty Hi, I am getting the below error after I upgrade Maven 2.2.1 to Maven 3.0. ... [ERROR] Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute (set-bastion-credentials) on project esb-parent-pom: java.lang.ClassCastException: script1286984516651 cannot be cast to groovy.lang.GroovyObject -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. ... This is the plugin that I am using. org.codehaus.groovy.maven gmaven-plugin But if I change the plugin like below, it is working. org.codehaus.gmaven gmaven-plugin 1.3 Is it mandatory to change the Gmaven plugin if I upgrade from maven 2.2.1 to 3.0? Please let me know, Thanks, Bodhayan. -- 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: (MASSEMBLY-510) leading period ('.') added to directory names
[
http://jira.codehaus.org/browse/MASSEMBLY-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239446#action_239446
]
KP commented on MASSEMBLY-510:
--
@John Casey: Yup, I just tried beta-4 and beta-5 and the result is the same.
> leading period ('.') added to directory names
> -
>
> Key: MASSEMBLY-510
> URL: http://jira.codehaus.org/browse/MASSEMBLY-510
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2
> Environment: Windows XP, SP3
> Maven 2.2.1
> Maven Assembly 2.2
>Reporter: KP
> Attachments: dist.xml, pom.xml
>
>
> $ cat dist.xml
> xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
> http://maven.apache.org/xsd/assembly-1.1.0.xsd";>
> dist
>
> zip
>
>
>
>
>
> ${project.basedir}/../paper
>
>
> ${project.basedir}/../boots
>
>
>
>
> $ mvn clean assembly:assembly
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building oracle-sql-assembly
> [INFO]task-segment: [clean]
> [INFO]
>
> [INFO] [clean:clean {execution: default-clean}]
> [INFO] Deleting directory F:\test-assembly\target
> [INFO]
>
> [INFO] Building oracle-sql-assembly
> [INFO]task-segment: [assembly:assembly] (aggregator-style)
> [INFO]
>
> [INFO] Preparing assembly:assembly
> [INFO]
>
> [INFO] Building oracle-sql-assembly
> [INFO]
>
> [INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
> [INFO] [assembly:assembly {execution: default-cli}]
> [INFO] Reading assembly descriptor: src/main/assembly/dist.xml
> [INFO] Building zip:
> F:\test-assembly\target\test-assembly-3.1-SNAPSHOT-dist.zip
> [INFO]
>
> [INFO] BUILD SUCCESSFUL
> [INFO]
>
> [INFO] Total time: 2 seconds
> [INFO] Finished at: Mon Oct 11 15:34:37 EDT 2010
> [INFO] Final Memory: 18M/45M
> [INFO]
>
> $ unzip -l target/test-assembly-dist.zip
> Archive: target/test-assembly-dist.zip
> Length DateTimeName
> - -- -
> 0 10-11-2010 15:34 test-assembly/
> 0 10-11-2010 15:27 test-assembly/.paper/
> 0 10-11-2010 15:27 test-assembly/.paper/random.txt
> 0 10-11-2010 15:27 test-assembly/.boots/
> 0 10-11-2010 15:27 test-assembly/.boots/boots.txt
> - ---
> 0 5 files
> Do you notice the '.paper' and '.boots' directories? It should just be
> 'paper' and 'boots', if I'm understanding it correctly.
> I tried other versions of the plugin (e.g., beta-4), I tried removing
> "${project.basedir}/".
> No go. :(
> P.S. If someone points me in the right direction, like a class name, I'll
> write a test case.
--
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-569) There should be a way to run unit tests from a dependency jar.
[ http://jira.codehaus.org/browse/SUREFIRE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239442#action_239442 ] Tim Pizey commented on SUREFIRE-569: @Max Andersen completely agree, I am amazed, in the light of http://maven.apache.org/guides/mini/guide-attached-tests.html at the existence of this bug. I jarred my tests in 2008, assuming that this was the expected use case, then blocked until now. I do not want to have to manually maintain the test suite, but that seems to be the only currently available mechanism. > There should be a way to run unit tests from a dependency jar. > -- > > Key: SUREFIRE-569 > URL: http://jira.codehaus.org/browse/SUREFIRE-569 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Reporter: Paul Gier > > In some cases it would be useful to have a set of tests that run with various > dependency configurations. One way to accomplish this would be to have a > single project that contains the unit tests and generates a test jar. > Several test configuration projects could then consume the unit tests and run > them with different dependency sets. The problem is that there is no easy > way to run tests in a dependency jar. The surefire plugin should have a > configuration to allow me to run all or a set of unit tests contained in a > dependency jar. -- 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-569) There should be a way to run unit tests from a dependency jar.
[ http://jira.codehaus.org/browse/SUREFIRE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239441#action_239441 ] Tim Pizey commented on SUREFIRE-569: The inheriting test suite can extend TestSuite or TestCase (or implement Test itself), but the suite() providing class should not extend either, or it too will be discovered my the Maven Surefire plugin and your tests will be run twice. > There should be a way to run unit tests from a dependency jar. > -- > > Key: SUREFIRE-569 > URL: http://jira.codehaus.org/browse/SUREFIRE-569 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Reporter: Paul Gier > > In some cases it would be useful to have a set of tests that run with various > dependency configurations. One way to accomplish this would be to have a > single project that contains the unit tests and generates a test jar. > Several test configuration projects could then consume the unit tests and run > them with different dependency sets. The problem is that there is no easy > way to run tests in a dependency jar. The surefire plugin should have a > configuration to allow me to run all or a set of unit tests contained in a > dependency jar. -- 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: (MJAVADOC-275) Creation of Javadoc attachments fails in multi-module project where modules have never been installed/deployed
[
http://jira.codehaus.org/browse/MJAVADOC-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239439#action_239439
]
Vincenzo Mancini commented on MJAVADOC-275:
---
The problem is still not fixed. Why the issue is closed?
> Creation of Javadoc attachments fails in multi-module project where modules
> have never been installed/deployed
> --
>
> Key: MJAVADOC-275
> URL: http://jira.codehaus.org/browse/MJAVADOC-275
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Benjamin Bentmann
>Assignee: John Casey
>Priority: Critical
> Fix For: 2.7
>
> Attachments: MJAVADOC-275.zip
>
>
> Running the commands
> {noformat}
> mvn clean
> mvn verify
> {noformat}
> will fail on the attached demo project with
> {noformat}
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc'
> has not be previously called for the project:
> 'org.apache.maven.its.javadoc:mod-b:jar:0.1'.
> Trying to invoke it...
> [ERROR] MavenInvocationException: Error when invoking Maven, consult the
> invoker log file:
> M:\MJAVADOC\mod-a\target\invoker\maven-javadoc-plugin625147587.txt
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] MavenReportException: Error while creating archive:
> Error when invoking Maven, consult the invoker log file:
> M:\MJAVADOC\mod-a\target\invoker\maven-javadoc-plugin625147587.txt
> {noformat}
> The command {{mvn clean verify}} as usually used during releases will also
> fail, but starts working after repeated invocations.
--
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: (MJAVADOC-276) Initial builds of a multi-module project fail
[
http://jira.codehaus.org/browse/MJAVADOC-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239438#action_239438
]
Vincenzo Mancini commented on MJAVADOC-276:
---
The problem is still there is not fixed. Why the issue is closed?
> Initial builds of a multi-module project fail
> -
>
> Key: MJAVADOC-276
> URL: http://jira.codehaus.org/browse/MJAVADOC-276
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.6.1
> Environment: Java jdk1.6.0_16, Maven 2.2.1, Windows Vista 64-bit
> Java jdk1.6.0_05, Maven 2.0.9, Windows XP 32-bit
>Reporter: Anthony Whitford
>Assignee: John Casey
>Priority: Blocker
> Fix For: 2.7
>
> Attachments: bug.zip, javadoctest.zip
>
>
> I ran into a problem using Maven Javadoc Plugin 2.6.1 right after I
> released... I went from version 1.15 to 1.16-SNAPSHOT, and my 1.16-SNAPSHOT
> build failed ({{mvn clean install site}}) because Javadoc fails when run from
> the top-level parent. When it is building _module A_, the javadoc complains
> that _module B_ and _module C_ are missing -- of course they are, they
> haven't been built yet. Note that running {{mvn clean install}} from _module
> A_ works fine -- the behavior is limited to running from the top-level parent
> -- AND, if you run a {{mvn install}} for _module B_ and _module C_, then you
> have given it what it needs and so you won't see the error.
> The attached example exhibits the problem. It was created from the
> _j2ee-simple_ archetype -- I only added the explicit javadoc plugin
> declaration to the top level pom to control the version being used. To
> recreate the problem, unzip and simply: {{mvn clean install site}}. You
> will get an error message like:
> {noformat}
> [INFO] Unable to find resource 'root.project.projects:logging:jar:1.0' in
> repository central (http://repo1.maven.org/maven2)
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Failed to resolve artifact.
> Missing:
> --
> 1) root.project.projects:logging:jar:1.0
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=root.project.projects
> -DartifactId=logging -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=root.project.projects
> -DartifactId=logging -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file
> -Durl=[url] -DrepositoryId=
> [id]
> Path to dependency:
> 1) root.project:primary-source:jar:1.0
> 2) root.project.projects:logging:jar:1.0
> --
> 1 required artifact is missing.
> for artifact:
> root.project:primary-source:jar:1.0
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> {noformat}
> As you can see, it seems to think that a submodule (in this case
> {{root.project.projects:logging:jar:1.0}}) is necessary to build the javadoc
> for the project... Since this is the first time that this is being built,
> the submodule does not exist (yet).
> I have replicated this problem on two different computing environments, so
> I'm convinced that the Maven version is not relevant.
> (It is unclear to me if this problem also existed with Javadoc 2.6, but I
> don't think so.)
--
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-569) There should be a way to run unit tests from a dependency jar.
[ http://jira.codehaus.org/browse/SUREFIRE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239436#action_239436 ] Max Andersen commented on SUREFIRE-569: --- Tim, that is correct. But no decent tessuite just contains a few test classes, it contains hundreds if not thousands of classes for testing. Having "AllSuites" for them all and requiring users to subclass them all to ensure it actually gets run is an unnecessary cumbersome step IMO. > There should be a way to run unit tests from a dependency jar. > -- > > Key: SUREFIRE-569 > URL: http://jira.codehaus.org/browse/SUREFIRE-569 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Reporter: Paul Gier > > In some cases it would be useful to have a set of tests that run with various > dependency configurations. One way to accomplish this would be to have a > single project that contains the unit tests and generates a test jar. > Several test configuration projects could then consume the unit tests and run > them with different dependency sets. The problem is that there is no easy > way to run tests in a dependency jar. The surefire plugin should have a > configuration to allow me to run all or a set of unit tests contained in a > dependency jar. -- 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-569) There should be a way to run unit tests from a dependency jar.
[
http://jira.codehaus.org/browse/SUREFIRE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239433#action_239433
]
Tim Pizey commented on SUREFIRE-569:
This can be done as follows (junit3):
Ensure test jar contains a class which has a static suite() method
import junit.framework.Test;
import junit.framework.TestSuite;
public class AllTests {
public static Test suite() {
TestSuite suite = new TestSuite(
"All Tests");
suite.addTestSuite(TestOne.class);
suite.addTestSuite(TestTwo.class);
return suite;
}
}
Then in the project using the test-jar dependency:
create a TestCase:
package org.melati.example.contacts;
import org.melati.poem.AllExportedTests;
import junit.framework.Test;
import junit.framework.TestCase;
public class PoemTest extends TestCase {
public static Test suite() {
return AllExportedTests.suite();
}
}
Now the tests will be found.
> There should be a way to run unit tests from a dependency jar.
> --
>
> Key: SUREFIRE-569
> URL: http://jira.codehaus.org/browse/SUREFIRE-569
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Surefire Plugin
>Reporter: Paul Gier
>
> In some cases it would be useful to have a set of tests that run with various
> dependency configurations. One way to accomplish this would be to have a
> single project that contains the unit tests and generates a test jar.
> Several test configuration projects could then consume the unit tests and run
> them with different dependency sets. The problem is that there is no easy
> way to run tests in a dependency jar. The surefire plugin should have a
> configuration to allow me to run all or a set of unit tests contained in a
> dependency jar.
--
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: (MJAVADOC-295) javadoc plugin version: 2.5, 2.6, 2.7 does not follow the reactor build sequence "mvn install site site:deploy"
[ http://jira.codehaus.org/browse/MJAVADOC-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239431#action_239431 ] Matthias Frenzel commented on MJAVADOC-295: --- JDK 6 Update 20 is used. > javadoc plugin version: 2.5, 2.6, 2.7 does not follow the reactor build > sequence "mvn install site site:deploy" > --- > > Key: MJAVADOC-295 > URL: http://jira.codehaus.org/browse/MJAVADOC-295 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.5, 2.6, 2.7 > Environment: Windows XP, Maven 2.2.1 >Reporter: Matthias Frenzel > > If i use the javadoc plugin version: 2.5, 2.6, 2.7 (these are the version > that i´ve checked). > "mvn install site-deploy does not follow the reactor build sequence" > and the complete build failed. > If i use the javadoc plugin version 2.4 it works correct. > Similar like: http://jira.codehaus.org/browse/MSITE-302 -- 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: (MCOMPILER-136) The description of the skip parameter of the testCompile mojo is incorrect
The description of the skip parameter of the testCompile mojo is incorrect -- Key: MCOMPILER-136 URL: http://jira.codehaus.org/browse/MCOMPILER-136 Project: Maven 2.x Compiler Plugin Issue Type: Bug Affects Versions: 2.3.2 Environment: n/a Reporter: Anders Hammar Priority: Trivial The description of the skip parameter of TestCompilerMojo should read: "Set this to 'true' to bypass compilation of test sources." I also think that the text "Its use is NOT RECOMMENDED, but quite convenient on occasion." should be removed. -- 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
