empty target/site/apidocs/apidocs/index.html created
Key: MJAVADOC-57
URL: http://jira.codehaus.org/browse/MJAVADOC-57
Project: Maven 2.x Javadoc Plugin
Type: Bug
Reporter: Brett Porter
Fix For: 2.0
thi
[
http://jira.codehaus.org/browse/MAVENUPLOAD-730?page=comments#action_58322 ]
Joerg Schaible commented on MAVENUPLOAD-730:
OK. Bundle updated again. You can continue. Thanks.
> Backport-util-concurrent-2.1
>
>
>
[
http://jira.codehaus.org/browse/MAVENUPLOAD-730?page=comments#action_58321 ]
Carlos Sanchez commented on MAVENUPLOAD-730:
javadocs are not supported yet, so shouldn't be included nor separate, nor in
the sources jar
> Backport-util-concurrent
[
http://jira.codehaus.org/browse/MAVENUPLOAD-730?page=comments#action_58320 ]
Joerg Schaible commented on MAVENUPLOAD-730:
OK, done, bundle is updated. The -sources.jar also contains the javadocs,
should that be a separate -javadoc(s).jar ? If
[ http://jira.codehaus.org/browse/MEV-282?page=all ]
Edwin Punzalan closed MEV-282:
--
Resolution: Fixed
Fixed.
NOTE: May take up to 4 hours for the fix to reach central repo.
> Please relocate jspapi:jsp-api to javax.servlet:jsp-api
>
Provide mechanism to change names of project (and possibly other) reports, etc.
in site
---
Key: MSITE-87
URL: http://jira.codehaus.org/browse/MSITE-87
Project: Maven 2.x Site Plugin
[ http://jira.codehaus.org/browse/MEV-295?page=all ]
Edwin Punzalan closed MEV-295:
--
Resolution: Fixed
Patch applied.
NOTE: May take up to 4 hours for the patch to reach central repo.
> dom4j optional dependencies
> ---
>
>
[
http://jira.codehaus.org/browse/MAVENUPLOAD-735?page=comments#action_58316 ]
Carlos Sanchez commented on MAVENUPLOAD-735:
Why 1.0.4?
> Please upload com.sun.xml:xalan 1.0.4
> -
>
> Key: MAVENUPLOAD-
[ http://jira.codehaus.org/browse/MAVENUPLOAD-734?page=all ]
Carlos Sanchez closed MAVENUPLOAD-734:
--
Assign To: Carlos Sanchez
Resolution: Fixed
Next time please ask before, as poms without jars need other processing
> Please upload jaxb-
[ http://jira.codehaus.org/browse/MAVENUPLOAD-733?page=all ]
Carlos Sanchez closed MAVENUPLOAD-733:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> Please upload jaxb-libs 1.0.4
> -
>
> Key: MAVENUPLOAD-
[ http://jira.codehaus.org/browse/MAVENUPLOAD-732?page=all ]
Carlos Sanchez closed MAVENUPLOAD-732:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> Please upload jaxb-impl 1.0.4
> -
>
> Key: MAVENUPLOAD-
[ http://jira.codehaus.org/browse/MPXDOC-134?page=all ]
Lukas Theussl closed MPXDOC-134:
Resolution: Won't Fix
Obsoleted by MPXDOC-130
> rewrite - scm support for xdoc plugin
> -
>
> Key: MPXDOC-134
>
[ http://jira.codehaus.org/browse/MPXDOC-161?page=all ]
Lukas Theussl updated MPXDOC-161:
-
Fix Version: (was: 1.10)
Needs more testing...
> Tabbed browsing for multiprojects (this change involves both the multiproject
> plugin and xdoc)
> -
[ http://jira.codehaus.org/browse/MPXDOC-114?page=all ]
Lukas Theussl closed MPXDOC-114:
Resolution: Fixed
Fix Version: 1.10
Fixed with MPXDOC-130
> cvs-usage presumes pserve protocol on
> --
>
[ http://jira.codehaus.org/browse/MPXDOC-130?page=all ]
Lukas Theussl closed MPXDOC-130:
Resolution: Fixed
> CVS Usage Page is blank when using Subversion scm.
> --
>
> Key: MPXDOC-130
>
[ http://jira.codehaus.org/browse/MAVENUPLOAD-738?page=all ]
Carlos Sanchez closed MAVENUPLOAD-738:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> Please upload jnp-client 4.0.2
> --
>
> Key: MAVENUPLOA
[ http://jira.codehaus.org/browse/MAVENUPLOAD-737?page=all ]
Carlos Sanchez closed MAVENUPLOAD-737:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> Please upload jbossmq-client 4.0.2
> --
>
> Key: MA
[ http://jira.codehaus.org/browse/MAVENUPLOAD-731?page=all ]
Carlos Sanchez closed MAVENUPLOAD-731:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> JasperReports 1.2.0
> ---
>
> Key: MAVENUPLOAD-731
> URL:
[ http://jira.codehaus.org/browse/MAVENUPLOAD-729?page=all ]
Carlos Sanchez closed MAVENUPLOAD-729:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> Sourceforge project 'dozer' to be uploaded.
> ---
>
[ http://jira.codehaus.org/browse/MAVENUPLOAD-728?page=all ]
Carlos Sanchez closed MAVENUPLOAD-728:
--
Assign To: Carlos Sanchez
Resolution: Duplicate
> Upload backport-util-concurrent version 2.1
> --
[
http://jira.codehaus.org/browse/MAVENUPLOAD-730?page=comments#action_58308 ]
Carlos Sanchez commented on MAVENUPLOAD-730:
sources have to be in jar format
> Backport-util-concurrent-2.1
>
>
> Key: MAVENUPL
[ http://jira.codehaus.org/browse/MAVENUPLOAD-727?page=all ]
Carlos Sanchez closed MAVENUPLOAD-727:
--
Assign To: Carlos Sanchez
Resolution: Fixed
Next time please make a bundle with jar and pom already in repository and
comment that only s
[
http://jira.codehaus.org/browse/MAVENUPLOAD-725?page=comments#action_58305 ]
Carlos Sanchez commented on MAVENUPLOAD-725:
Please add the url where this can be downloaded from displaytag to make a
decision about naming.
Group has to be displayt
This explains everything. I thought you wanted to deploy the actual
myfaces jars. As soon as stuff is signed and checksummed we'll proceed
On 2/9/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
> On 2/9/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> > groupid should be org.apache.myfaces
>
> I disa
Issue Subscription
Filter: Design & Best Practices (32 issues)
Subscriber: mavendevlist
Key Summary
MNG-612 implement conflict resolution techniques
http://jira.codehaus.org/browse/MNG-612
MNG-1931add a reportingManagement section
http://jira.codehaus.org/b
[ http://jira.codehaus.org/browse/MNG-2047?page=all ]
Allan Ramirez closed MNG-2047:
--
Resolution: Fixed
Sure thing :)
> doc. "Philosophy of Maven": Typo
>
>
> Key: MNG-2047
> URL: http://jira.codehaus
Ok - I was just going on Carlos' questions, but I think you answered
them in the other mail.
It is a manual sync, but please sign the plugin JAR beforehand (see the
README.txt in the root for a list of prerequisites).
- Brett
Sean Schofield wrote:
>> Could I just ask that we experiment with this
> Could I just ask that we experiment with this in the snapshot repository
> first? The /dist/ directory is mirrored worldwide and I'd prefer the
> final releases go in there once everyone is happy.
Sure except this wasn't an experiment ;-) We have released the POM
and we're trying to publish it.
On 2/9/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> groupid should be org.apache.myfaces
I disagree. We want separate groupids for each of our major
subprojects. Otherwise you have some twenty artifacts lumped together
in the repo. Since the group id is more or less arbitrary (like a
package
[ http://jira.codehaus.org/browse/MRM-36?page=comments#action_58302 ]
Brett Porter commented on MRM-36:
-
I'd like to see some thoughts on how this will be implemented before diving in
to it. Also, bear in mind the scheduling is not yet integrated into the we
[ http://jira.codehaus.org/browse/MRM-68?page=all ]
Maria Odea Ching closed MRM-68:
---
Resolution: Fixed
The resolution is included in the patch file attached in MRM-69.
> Accomodate "query everything" in the index
> ---
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060210.003002.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060210.003002.txt
-
To unsubscribe, e-mai
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060210.01.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060210.01.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Distribution:
http://maven.zones.apache.org/~continuum/builds/trunk/continuum-20060209.230001.war
Log:
http://maven.zones.apache.org/~continuum/logs/trunk/continuum-build-log-20060209.230001.txt
[ http://jira.codehaus.org/browse/MNGECLIPSE-39?page=comments#action_58294
]
Eugene Kuleshov commented on MNGECLIPSE-39:
---
Darren, in my opinion PDE editor, and in particular the page you've attached is
the least user friendly piece of UI I ever de
[ http://jira.codehaus.org/browse/MEAR-18?page=comments#action_58292 ]
Brett Porter commented on MEAR-18:
--
Brad, can you supply a patch instead?
svn diff >MEAR-18.diff
> The EAR plugin will not properly handle WSR (Jboss web service archives)
> specified
[ http://jira.codehaus.org/browse/MEAR-18?page=all ]
Brad O'Hearne updated MEAR-18:
--
Attachment: maven-ear-plugin.tar.gz
> The EAR plugin will not properly handle WSR (Jboss web service archives)
> specified as dependencies in the pom.xml
> ---
[ http://jira.codehaus.org/browse/MNGECLIPSE-39?page=all ]
Darren Bell updated MNGECLIPSE-39:
--
Attachment: example-plugin-xml-editor.jpg
> POM editor
> --
>
> Key: MNGECLIPSE-39
> URL: http://jira.codehaus.org/browse/MNGECLIPSE
Log:
http://maven.zones.apache.org/~continuum/logs/branches/continuum-1.0.x/continuum-build-log-20060209.223000.txt
[ http://jira.codehaus.org/browse/CONTINUUM-584?page=all ]
Emmanuel Venisse closed CONTINUUM-584:
--
Resolution: Fixed
Fixed.
It's set for checkout and update, is it correct?
> Continuum needs to set checkouts persistent
> --
[ http://jira.codehaus.org/browse/MRELEASE-80?page=all ]
Brett Porter closed MRELEASE-80:
Assign To: Brett Porter
Resolution: Fixed
Fix Version: 2.0-beta-4
this was fixed in SVN last october
> release:prepare incorrectly Runtime.exec's m
[ http://jira.codehaus.org/browse/MNGECLIPSE-39?page=comments#action_58286
]
Darren Bell commented on MNGECLIPSE-39:
---
Might i suggest an editor like the PDE? You could use EMF to map the pom to an
ecore model. A multi page eclipse forms editor would
[ http://jira.codehaus.org/browse/CONTINUUM-537?page=all ]
Emmanuel Venisse closed CONTINUUM-537:
--
Assign To: Emmanuel Venisse
Resolution: Fixed
Fixed.
> Guests cannot see totals
>
>
> Key: CONTINUUM-537
Could I just ask that we experiment with this in the snapshot repository
first? The /dist/ directory is mirrored worldwide and I'd prefer the
final releases go in there once everyone is happy.
Thanks,
Brett
Carlos Sanchez wrote:
> groupid should be org.apache.myfaces
>
> Some questions:
> - what
[ http://jira.codehaus.org/browse/MAVEN-1716?page=all ]
Benjamin Dang updated MAVEN-1716:
-
Attachment: screenshot-1.jpg
> Download problem from internal repository
> -
>
> Key: MAVEN-1716
> URL: h
[ http://jira.codehaus.org/browse/MAVEN-1716?page=comments#action_58283 ]
Benjamin Dang commented on MAVEN-1716:
--
Seems this issue is fixed. There are at least two types of repositories: a
general library repository and plugin repository. In the plugi
[ http://jira.codehaus.org/browse/CONTINUUM-527?page=all ]
Emmanuel Venisse closed CONTINUUM-527:
--
Assign To: Emmanuel Venisse
Resolution: Fixed
Done.
> Getting Started Documentation omits JAVA_HOME requirement
> -
[ http://jira.codehaus.org/browse/CONTINUUM-543?page=all ]
Emmanuel Venisse closed CONTINUUM-543:
--
Assign To: Emmanuel Venisse
Resolution: Fixed
Applied.
> please add reference to netbeans continuum integration from the the continuum
> s
+1
I'd like to give it a once over first, but I see no reason this isn't a
1.0 release.
- Brett
John Casey wrote:
> Hi everyone,
>
> I'm not sure who's using this plugin, other than Hiram :), but I think
> if he's using it on a regular basis and thinks it's ready for a first
> release, we shoul
[ http://jira.codehaus.org/browse/CONTINUUM-531?page=all ]
Emmanuel Venisse closed CONTINUUM-531:
--
Resolution: Fixed
Applied.
> Add back the "build now" button on the "view project" page.
> -
Please upload jnp-client 4.0.2
--
Key: MAVENUPLOAD-738
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-738
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
Part of JBoss application server 4.0.2
--
This message is a
Hi,
I think it'd be useful to create a project with mock objects, eg
Artifact, MavenProject,... as I have already seen some implementations
in plugins test (eg. jar plugin), to avoid repetition and make it easy
to test stuff. it doesn't mean start making mocks right now, but
setting up a place whe
Please upload jbossmq-client 4.0.2
--
Key: MAVENUPLOAD-737
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-737
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
Part of JBoss application server 4.0.2
--
This mess
+1
The cargo project uses it to build the m1 plugin with m2
Arnaud
On 2/9/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> +1 Whoot!
>
> /Hiram
>
> On Feb 9, 2006, at 3:57 PM, John Casey wrote:
>
> > Hi everyone,
> >
> > I'm not sure who's using this plugin, other than Hiram :), but I
> > think if
Please upload com.sun.xml:xercesImpl 1.0.4
--
Key: MAVENUPLOAD-736
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-736
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
Part of the Java Web Services Develop
[ http://jira.codehaus.org/browse/MJAR-20?page=comments#action_58276 ]
Carlos Sanchez commented on MJAR-20:
Another use case
parent pom attaching test jar, maven creates an empty test jar for that pom
project
> Don't create empty jars
> ---
Please upload com.sun.xml:xalan 1.0.4
-
Key: MAVENUPLOAD-735
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-735
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
Part of the Java Web Services Developer Pack 1.
Please upload jaxb-xjc 1.0.4
Key: MAVENUPLOAD-734
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-734
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
Part of the Java Web Services Developer Pack 1.5
Bundle contains
Please upload jaxb-libs 1.0.4
-
Key: MAVENUPLOAD-733
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-733
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
Part of the Java Web Services Developer Pack 1.5
Bundle contain
Please upload jaxb-impl 1.0.4
-
Key: MAVENUPLOAD-732
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-732
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
Part of the Java Web Services Developer Pack 1.5
Bundle contain
+1 Whoot!
/Hiram
On Feb 9, 2006, at 3:57 PM, John Casey wrote:
Hi everyone,
I'm not sure who's using this plugin, other than Hiram :), but I
think if he's using it on a regular basis and thinks it's ready for
a first release, we should consider moving it out of the sandbox
and putting t
John Casey wrote:
Hi everyone,
I'm not sure who's using this plugin, other than Hiram :), but I think
if he's using it on a regular basis and thinks it's ready for a first
release, we should consider moving it out of the sandbox and putting
together a first release for it.
WDYT?
Please add
groupid should be org.apache.myfaces
Some questions:
- what's the difference between the pom.xml and the
master-pom/pom.xml? why two and not just one with both info?
- why do you have a maven-wagon-plugin?
- this is maven related stuff, where is the myfaces stuff?
On 2/9/06, Sean Schofield <[EMAI
Sorry, I sent this to Carlos directly instead of the list.
Sean
-- Forwarded message --
From: Sean Schofield <[EMAIL PROTECTED]>
Date: Feb 9, 2006 4:20 PM
Subject: Re: Where do I publish ASF Project Jars?
To: Carlos Sanchez <[EMAIL PROTECTED]>
On 2/9/06, Carlos Sanchez <[EMAIL P
+1 but it's always in sandbox.
Emmanuel
John Casey a écrit :
Hi everyone,
I'm not sure who's using this plugin, other than Hiram :), but I think
if he's using it on a regular basis and thinks it's ready for a first
release, we should consider moving it out of the sandbox and putting
togethe
Hi everyone,
I'm not sure who's using this plugin, other than Hiram :), but I think
if he's using it on a regular basis and thinks it's ready for a first
release, we should consider moving it out of the sandbox and putting
together a first release for it.
WDYT?
Please add your +1/0/-1, and
[ http://jira.codehaus.org/browse/MNG-2059?page=comments#action_58274 ]
Mike Whittemore commented on MNG-2059:
--
Yes, and I do it wherever I can. Here's why I feel the "grouping" funtionality
would be beneficial:
We organize our projects based on their
wagon-http dos not handle HTTP 204 No Content code as success
-
Key: WAGONHTTP-7
URL: http://jira.codehaus.org/browse/WAGONHTTP-7
Project: wagon-http
Type: Bug
Versions: 1.0-alpha-6
Environment: Li
[ http://jira.codehaus.org/browse/MNG-2059?page=comments#action_58272 ]
Emmanuel Venisse commented on MNG-2059:
---
Have you try this:
in parent pom:
your_groupId
your_artifactId
your_version
pom
in child pom:
Hi Sean,
www.apache.org/dist/java-repository/myfaces is for maven 1
www.apache.org/dist/maven-repository/org/apache/myfaces is for maven 2
Both places are only for PMC approved releases, copied to ibiblio (m1
automatically, m2 on demand)
For not releases (snapshots or nightly builds), and not mir
release:prepare incorrectly Runtime.exec's m2 instead of mvn
Key: MRELEASE-80
URL: http://jira.codehaus.org/browse/MRELEASE-80
Project: Maven 2.x Release Plugin
Type: Bug
Environment: Linux/x86_64, FC4, j
Greetings,
I'm with the MyFaces project and we're now learning "the Maven way."
We are trying to publish our first jars to the Maven repo. In the
past we were asked to copy our jars files manually to
www.apache.org/dist/java-repository/myfaces/...
The latest ASF documentation seems to suggest
[ http://jira.codehaus.org/browse/MEV-329?page=all ]
Carlos Sanchez closed MEV-329:
--
Assign To: Carlos Sanchez
Resolution: Fixed
Will be available in ibiblio in the following hours
About mirrors, we don't support them, we only publish them for us
[ http://jira.codehaus.org/browse/MNG-2037?page=comments#action_58266 ]
Michael Böckling commented on MNG-2037:
---
Just wanted to say that I have a similar issue where I get a NPE in Solaris,
but not in Windows, maybe these are related? I'm trying to inv
[ http://jira.codehaus.org/browse/MEV-329?page=comments#action_58265 ]
Daniel Kulp commented on MEV-329:
-
One more note: the version on mirrors.dotsrc.org DOES work. Apparently
mirrors.dotsrc.org is not really in sync with ibiblio. That may be a separate
[ http://jira.codehaus.org/browse/MEV-329?page=comments#action_58264 ]
Daniel Kulp commented on MEV-329:
-
Actually, it's PMD that breaks, not antrun. However, we use antrun to call
PMD (variety of reasons) so now that PMD doesn't work, antrun doesn't work
The generated "get-deps" target uses the "get" target - would be better to use
Maven Ant Tasks
--
Key: MANT-8
URL: http://jira.codehaus.org/browse/MANT-8
Project: Maven 2.x Ant Plugi
"test" target should support running a single test - just like mvn test does
Key: MANT-7
URL: http://jira.codehaus.org/browse/MANT-7
Project: Maven 2.x Ant Plugin
Type: Improvement
Repo
"test" targets should fail if junit.jar not present
---
Key: MANT-6
URL: http://jira.codehaus.org/browse/MANT-6
Project: Maven 2.x Ant Plugin
Type: Improvement
Reporter: Matt Raible
IMO, it's better to fail than
[ http://jira.codehaus.org/browse/MEV-329?page=comments#action_58263 ]
Trygve Laugstol commented on MEV-329:
-
The scope should be provided as well.
> http://www.ibiblio.org/maven2/xom/xom/1.0b3/xom-1.0b3.pom is not correct
> -
Add line breaks between elements in build.xml
--
Key: MANT-5
URL: http://jira.codehaus.org/browse/MANT-5
Project: Maven 2.x Ant Plugin
Type: Improvement
Reporter: Matt Raible
Priority: Minor
Most folks t
[ http://jira.codehaus.org/browse/MNG-2037?page=all ]
Olivier Lamy closed MNG-2037:
-
Resolution: Cannot Reproduce
I can't reproduce it.
Sorry for noise.
> Strange NPE with profile and injectPlugins
> --
>
>
http://www.ibiblio.org/maven2/xom/xom/1.0b3/xom-1.0b3.pom is not correct
Key: MEV-329
URL: http://jira.codehaus.org/browse/MEV-329
Project: Maven Evangelism
Type: Bug
Components: Invalid POM
Hi Guys,
I need a release of the org.apache.maven.plugins:maven-one-plugin
plugin. My project depends on it an I can't release until it's
released.
Regards,
Hiram
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Distribution:
http://maven.zones.apache.org/~continuum/builds/trunk/continuum-20060209.18.war
Log:
http://maven.zones.apache.org/~continuum/logs/trunk/continuum-build-log-20060209.18.txt
[ http://jira.codehaus.org/browse/MPJDEPEND-7?page=comments#action_58259 ]
Lukas Theussl commented on MPJDEPEND-7:
---
What is the actual error you are getting?
The description of the maven.jdepend.components property is unfortunately a
documentation bug
The build fails when it tries to get the latest version of the project.
There isn't an error in the log, it just never seems to make it past the
sync command. If I run the p4 sync command exactly as it's printed in the
log, the sync works. Also, if I run the sync command in the Continuum
working
Add ability to depend on a group of dependencies with a single dependency
element.
--
Key: MNG-2059
URL: http://jira.codehaus.org/browse/MNG-2059
Project: Maven 2
Type: New Feature
Env
[ http://jira.codehaus.org/browse/MASSEMBLY-11?page=comments#action_58252 ]
Manfred Geiler commented on MASSEMBLY-11:
-
Ok, just realized that the variable resolving is already addressed in
MASSEMBLY-40.
> In a multi-module build, assembly descriptor
[ http://jira.codehaus.org/browse/MASSEMBLY-11?page=comments#action_58251 ]
Manfred Geiler commented on MASSEMBLY-11:
-
I have the same problem and hope that this can be fixed soon. In my current
project I attached the assembly to the install phase an
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060209.154501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060209.154501.txt
-
To unsubscribe, e-mai
Cannot generate report without component property set
-
Key: MPJDEPEND-7
URL: http://jira.codehaus.org/browse/MPJDEPEND-7
Project: maven-jdepend-plugin
Type: Bug
Versions: 1.6
Environment: Windows, Maven 1
You should give the Maven embedder a try. It's used to do something
similar in the maven-it-plugin:
https://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-it-plugin
HTH,
John
Alex Karasulu wrote:
Hi,
I have a plugin that needs to checkout some resources then trigger a
'mvn site' on t
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060209.153001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060209.153001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060209.144501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060209.144501.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MECLIPSE-3?page=comments#action_58232 ]
Olivier Lamy commented on MECLIPSE-3:
-
workaround :
mvn -Dmaven.test.skip=true clean compile eclipse:clean eclipse:eclipse
> Generation of eclipse projects requires that reactor pr
[ http://jira.codehaus.org/browse/MECLIPSE-3?page=comments#action_58230 ]
Olivier Lamy commented on MECLIPSE-3:
-
The title should be :
eclipse:eclipse requires target/classes directories present for project
references.
see relative http://jira.codehaus.o
[ http://jira.codehaus.org/browse/MECLIPSE-67?page=all ]
Kenney Westerhof closed MECLIPSE-67:
Resolution: Duplicate
Fix Version: 2.1
After extensive testing with Olivier we found out his issue was actually a
known one,
being that target/cl
Log:
http://maven.zones.apache.org/~continuum/logs/branches/continuum-1.0.x/continuum-build-log-20060209.093001.txt
JasperReports 1.2.0
---
Key: MAVENUPLOAD-731
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-731
Project: maven-upload-requests
Type: Task
Reporter: lucian chirita
Free (LGPL) Java reporting library. Includes sources.
--
This message is aut
1 - 100 of 116 matches
Mail list logo
