Arnaud,
I checked what you did in javadoc and I don't think I can do it the same
way. You basically introduced a new variable that you set to true the
first time a goal is called, and then you check this variable to make
sure the same goal doesn't get called again. The problem with xdoc:init
[ http://jira.codehaus.org/browse/MPCHECKSTYLE-28?page=all ]
Lukas Theussl closed MPCHECKSTYLE-28:
-
Resolution: Won't Fix
Fix Version: (was: 3.0.1)
I'd rather not change this as it might break the behavior expected by some
people
[ http://jira.codehaus.org/browse/MPCHECKSTYLE-52?page=all ]
Lukas Theussl closed MPCHECKSTYLE-52:
-
Resolution: Fixed
The links to jxr files should use maven.jxr.destdir and
maven.jxr.destdir.test
I forgot to mention: if you want to read something about upgrading
dom4j, here are a few links to begin with:
http://jira.codehaus.org/browse/MAVEN-1345
http://jira.codehaus.org/browse/JAXEN-67
http://issues.apache.org/jira/browse/JELLY-226
Have fun!
-Lukas
Nicolas De Loof wrote:
I've
[ http://jira.codehaus.org/browse/MAVEN-1744?page=all ]
Lukas Theussl closed MAVEN-1744:
Resolution: Won't Fix
Please only open issues in JIRA if you are sure that there is actually a bug.
Otherwise ask on the mailing list first.
A cycle
[ http://jira.codehaus.org/browse/MPJNLP-29?page=comments#action_58621 ]
Lukas Theussl commented on MPJNLP-29:
-
The jnlp plugin has just been demoted to the Maven sandbox, it is not
officially maintained by us anymore. If you are interested
[ http://jira.codehaus.org/browse/MAVEN-1743?page=all ]
Lukas Theussl closed MAVEN-1743:
Resolution: Won't Fix
Please only open issues in JIRA if you are sure that there is actually a bug.
Otherwise ask on the mailing list first.
In your case you
Nicolas,
Have you played around with the maven.docs.outputencoding property? You
might also have a look here for some tips on a similar problem:
http://jira.codehaus.org/browse/MPXDOC-184
If you can't get it to work, please open an issue in JIRA with a small
reproducible test case. Thanks!
[ http://jira.codehaus.org/browse/MPJDEPEND-7?page=all ]
Lukas Theussl closed MPJDEPEND-7:
-
Resolution: Fixed
Cannot generate report without component property set
-
Key: MPJDEPEND-7
[ http://jira.codehaus.org/browse/MPXDOC-181?page=all ]
Lukas Theussl reopened MPXDOC-181:
--
xdoc:init is called 6 times
---
Key: MPXDOC-181
URL: http://jira.codehaus.org/browse/MPXDOC-181
Project
[ http://jira.codehaus.org/browse/MPXDOC-181?page=all ]
Lukas Theussl closed MPXDOC-181:
Resolution: Fixed
Fix Version: 1.10
I fixed this by introducing new -noinit goals for all goals that are called
internally.
Goals that existed before
Include dependencies' scope in dependencies page
Key: MPXDOC-191
URL: http://jira.codehaus.org/browse/MPXDOC-191
Project: maven-xdoc-plugin
Type: Improvement
Reporter: Lukas Theussl
Priority: Minor
Fix
Include the new maven-stylus.css theme
--
Key: MPXDOC-190
URL: http://jira.codehaus.org/browse/MPXDOC-190
Project: maven-xdoc-plugin
Type: Improvement
Environment: m11b3
Reporter: Lukas Theussl
Priority: Minor
Fix
I have put my comments into the README.txt files.
Basically, I think we should keep the schema files of published versions
in src/dtd/maven-xdoc-{version}.dtd, while the current development
version is src/plugin-resources/dtd/maven-xdoc.dtd. I don't think it is
abolutely necessary but it
[ http://jira.codehaus.org/browse/MPXDOC-190?page=all ]
Lukas Theussl closed MPXDOC-190:
Resolution: Fixed
Include the new maven-stylus.css theme
--
Key: MPXDOC-190
URL: http
[ http://jira.codehaus.org/browse/MPXDOC-191?page=all ]
Lukas Theussl closed MPXDOC-191:
Resolution: Fixed
Include dependencies' scope in dependencies page
Key: MPXDOC-191
URL
I am seeing some weird layout problems when using stylus with some of my
custom projects, until I don't understand where that comes from, I
prefer not to use it by default.
I don't know what you mean with 'cleanup our project.css', we are not
using any project.css files?
-Lukas
Arnaud
Brett Porter wrote:
Please *don't* use it by default. In fact, I see no reason why this
should have been included in the xdoc plugin.
Is there a particular reason not to include it? I thought, since we have
it already, we might as well use it and make it available. I am not in
favor of
Brett Porter wrote:
I guess they make a big difference - either way is fine. But if it isn't
working, probably best to leave it out until it is?
It turned out that the layout problems I experienced in some projects
were due to an organization logo that was too big. That had the strange
]
Lukas Theussl commented on MAVEN-1742:
--
Did you declare commons-jelly-tags-velocity in your project dependencies?
From the information you give above it is still not clear what you are doing,
what is the goal you ran that lead this error?
Could not find
[ http://jira.codehaus.org/browse/MAVEN-1742?page=all ]
Lukas Theussl updated MAVEN-1742:
-
Fix Version: (was: 1.0.2)
Summary:
Could not find the class:
org.apache.commons.jelly.tags.velocity.VelocityTagLibrary
ary
was:
Could not find
[ http://jira.codehaus.org/browse/MPCHECKSTYLE-24?page=all ]
Lukas Theussl closed MPCHECKSTYLE-24:
-
Resolution: Won't Fix
Fix Version: (was: 3.0.1)
The original problem should be fixed by putting property name=headerFile
value
: m11b3
Reporter: Lukas Theussl
Fix For: 3.0.1
From MPCHECKSTYLE-24:
I have an issue with the new checkstyle plugin version (3.0) too when running
in a multiproject build.
The problem is, is that the checkstyle files are now by default generated under
the /target/checkstyle dir. When
Why is this not enough? [1] only talks about three +1 votes and no
vetos, it doesn't mention binding votes for package releases.
(Just being curious, I think I did some of my releases without 3 binding
votes as well...)
-Lukas
[1] http://www.apache.org/foundation/voting.html
Brett Porter
heard it said in other places that you need 3 pmc
votes.
- Brett
Lukas Theussl wrote:
Why is this not enough? [1] only talks about three +1 votes and no
vetos, it doesn't mention binding votes for package releases.
(Just being curious, I think I did some of my releases without 3 binding
votes
[
http://jira.codehaus.org/browse/MPCHECKSTYLE-20?page=comments#action_58477 ]
Lukas Theussl commented on MPCHECKSTYLE-20:
---
Jeff, could you attach a small test project? I don't know how to reproduce this.
Unable to get class information
Document the use of dependency.properties.comment
-
Key: MPXDOC-189
URL: http://jira.codehaus.org/browse/MPXDOC-189
Project: maven-xdoc-plugin
Type: Task
Reporter: Lukas Theussl
Fix For: 1.10
Upgrade to xalan-2.7.0
--
Key: MPPDF-55
URL: http://jira.codehaus.org/browse/MPPDF-55
Project: maven-pdf-plugin
Type: Task
Environment: m11b3
Reporter: Lukas Theussl
Fix For: 2.5
The xerces jars that go with it are xercesImpl-2.7.1
[ http://jira.codehaus.org/browse/MPXDOC-161?page=comments#action_58386 ]
Lukas Theussl commented on MPXDOC-161:
--
Hi Ignacio,
I haven't found any errors because I haven't had time to really test it. For
the m1 development in general, due to lack
[ http://jira.codehaus.org/browse/MPJDEPEND-7?page=comments#action_58387 ]
Lukas Theussl commented on MPJDEPEND-7:
---
Yes, the current jdepend plugin assumes that you have a package element in your
pom.
I think it is a good idea to have one (it is also
[ http://jira.codehaus.org/browse/MPJDEPEND-7?page=all ]
Lukas Theussl updated MPJDEPEND-7:
--
Fix Version: 1.6.1
Cannot generate report without component property set
-
Key: MPJDEPEND-7
+1
-Lukas
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.
[ http://jira.codehaus.org/browse/MPJDEPEND-7?page=comments#action_58388 ]
Lukas Theussl commented on MPJDEPEND-7:
---
I have deployed a SNAPSHOT:
maven plugin:download
-Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository
[ http://jira.codehaus.org/browse/MPJAVADOC-73?page=all ]
Lukas Theussl closed MPJAVADOC-73:
--
Resolution: Won't Fix
Javadoc Warnings report is empty, has parse exception
-
Key
[ http://jira.codehaus.org/browse/MPXDOC-189?page=all ]
Lukas Theussl closed MPXDOC-189:
Resolution: Fixed
Document the use of dependency.properties.comment
-
Key: MPXDOC-189
[ 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
[ 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/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 connection
[ 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-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/MPASPECTJ-19?page=all ]
Lukas Theussl closed MPASPECTJ-19:
--
Resolution: Fixed
Fixed a while ago.
Add messageHolderClass property
---
Key: MPASPECTJ-19
URL: http
[ http://jira.codehaus.org/browse/MPASPECTJ-23?page=all ]
Lukas Theussl updated MPASPECTJ-23:
---
Fix Version: 3.3
Report for the plugin
-
Key: MPASPECTJ-23
URL: http://jira.codehaus.org/browse/MPASPECTJ-23
[ http://jira.codehaus.org/browse/MPSCM-77?page=all ]
Lukas Theussl closed MPSCM-77:
--
Resolution: Fixed
I finally opted for a new property maven.scm.testmode (default: false) which
was easier to implement (otherwise we would have had to check whether
[ http://jira.codehaus.org/browse/MPSCM-67?page=comments#action_58164 ]
Lukas Theussl commented on MPSCM-67:
Dennis,
I think with the fix for MPSCM-77 you should have a workaround for your problem
(it allows you to remove the backup files by hand before
[ http://jira.codehaus.org/browse/MPXDOC-185?page=all ]
Lukas Theussl closed MPXDOC-185:
Resolution: Fixed
maven.xdoc.date=navigation-top and navigation-bottom do not work
[ http://jira.codehaus.org/browse/MPWAR-33?page=all ]
Lukas Theussl reopened MPWAR-33:
Plugin generates multiple Class-Path entries in the manifest file
-
Key: MPWAR-33
[ http://jira.codehaus.org/browse/MPWAR-22?page=all ]
Lukas Theussl closed MPWAR-22:
--
Resolution: Fixed
Fix Version: (was: 1.7)
1.6.1
war manifest file can't be specified like ejb and jar plugins
[ http://jira.codehaus.org/browse/MPWAR-33?page=all ]
Lukas Theussl updated MPWAR-33:
---
Fix Version: (was: 1.7)
1.6.1
Plugin generates multiple Class-Path entries in the manifest file
[ http://jira.codehaus.org/browse/MPWAR-33?page=all ]
Lukas Theussl closed MPWAR-33:
--
Resolution: Fixed
Plugin generates multiple Class-Path entries in the manifest file
[ http://jira.codehaus.org/browse/MPWAR-22?page=all ]
Lukas Theussl reopened MPWAR-22:
Assign To: (was: dion gillard)
war manifest file can't be specified like ejb and jar plugins
Sorry, I just thought this order was more logical (changelog,
file/dev-activity together, license in the end,...). I'll check the
sandbox as well.
-Lukas
Arnaud HERITIER wrote:
I just use the alphabetical order.
Why this order ?
It's for the order in the menu ?
Be careful to apply the same
+1 (read and agree).
Just make sure we have someone willing to keep them maintained to avoid
the mess we have in m1 now.
-Lukas
Brett Porter wrote:
This is not a vote. +1's here are just I've read and think it's all
good, but generally I'm just looking for feedback on specific plugins
[ http://jira.codehaus.org/browse/MPDASHBOARD-28?page=comments#action_58076
]
Lukas Theussl commented on MPDASHBOARD-28:
--
For the record: introduced maven.dashboard.sort and
maven.dashboard.sort.property properties.
Please sorth the report
[
http://jira.codehaus.org/browse/MPCHECKSTYLE-53?page=comments#action_58077 ]
Lukas Theussl commented on MPCHECKSTYLE-53:
---
It's not a problem with checkstyle itself but with ant's style task that is
used to transform the results. Did you load
[
http://jira.codehaus.org/browse/MPCHECKSTYLE-53?page=comments#action_58086 ]
Lukas Theussl commented on MPCHECKSTYLE-53:
---
I have deployed a new snapshot, please test:
maven plugin:download
-Dmaven.repo.remote=http://www.ibiblio.org/maven,http
[
http://jira.codehaus.org/browse/MPCHECKSTYLE-53?page=comments#action_58093 ]
Lukas Theussl commented on MPCHECKSTYLE-53:
---
I used this version for compatibility with other plugins.
We are considering upgrading xalan (see the comments at MPPDF-51
[ http://jira.codehaus.org/browse/MPCHECKSTYLE-53?page=all ]
Lukas Theussl closed MPCHECKSTYLE-53:
-
Resolution: Fixed
ClassCastException when moving from 2.5 to 3.0
--
Key: MPCHECKSTYLE
[ http://jira.codehaus.org/browse/MPXDOC-181?page=all ]
Lukas Theussl closed MPXDOC-181:
Resolution: Won't Fix
Fix Version: (was: 1.10)
This should be fixed with MAVEN-256 before Maven 1.1 final.
xdoc:init is called 6 times
[ http://jira.codehaus.org/browse/MPCHECKSTYLE-9?page=all ]
Lukas Theussl closed MPCHECKSTYLE-9:
Resolution: Fixed
Checkstyle plugin doesn't respect maven.license.licenseFile
[ http://jira.codehaus.org/browse/MPXDOC-181?page=comments#action_58109 ]
Lukas Theussl commented on MPXDOC-181:
--
No I am not sure. I just saw Brett's comment: 'We need to define the behaviour,
provide a way to do both, and leave it for 1.1 so we don't
[ http://jira.codehaus.org/browse/MPJAVADOC-73?page=comments#action_58110 ]
Lukas Theussl commented on MPJAVADOC-73:
Can you try to add a prereqs=xdoc:init to the maven-javadoc-plugin:register
goal in plugin.jelly of the javadoc plugin?
Javadoc
[ http://jira.codehaus.org/browse/MPCHECKSTYLE-38?page=all ]
Lukas Theussl closed MPCHECKSTYLE-38:
-
Resolution: Fixed
RSS file has incorrect dir paths generated for use in Maven multiproject site
[ http://jira.codehaus.org/browse/MAVEN-1664?page=all ]
Lukas Theussl closed MAVEN-1664:
Resolution: Cannot Reproduce
Must have been fixed at one point ...
trim property values
Key: MAVEN-1664
URL: http
[ http://jira.codehaus.org/browse/MPEAR-44?page=all ]
Lukas Theussl closed MPEAR-44:
--
Assign To: Lukas Theussl (was: Stephane Nicoll)
Resolution: Fixed
Move resolver tag from j2ee to ear
--
Key: MPEAR
: maven-scm-plugin
Type: Improvement
Environment: m11b3, scm plugin
Reporter: Lukas Theussl
Priority: Critical
Fix For: 1.6
See MRELEASE-77 for the equivalent m2 problem.
Currently, the scm:prepare-release goal modifies the files project.xml and
changes.xml, then commits
I'll check it but I don't know if we are allowed to do big code changes
after a vote. It's just a minor issue, IMO we could leave it for a
bugfix release a bit later (there are a few minor issues open still that
should be easy to fix). WDYT?
-Lukas
Arnaud HERITIER wrote:
Hi lukas, I didn't
[ http://jira.codehaus.org/browse/MPCHECKSTYLE-9?page=all ]
Lukas Theussl updated MPCHECKSTYLE-9:
-
Fix Version: 3.0.1
Checkstyle plugin doesn't respect maven.license.licenseFile
Type: Bug
Versions: 3.0
Environment: m11b3
Reporter: Lukas Theussl
Fix For: 3.0.1
Check the corresponding files in the pmd plugin.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http
[ http://jira.codehaus.org/browse/MPCHECKSTYLE-38?page=all ]
Lukas Theussl updated MPCHECKSTYLE-38:
--
Fix Version: 3.0.1
RSS file has incorrect dir paths generated for use in Maven multiproject site
[ http://jira.codehaus.org/browse/MPCHECKSTYLE-28?page=all ]
Lukas Theussl updated MPCHECKSTYLE-28:
--
Fix Version: 3.0.1
maven.checkstyle.fail.on.violation make the site generation fail
[ http://jira.codehaus.org/browse/MPCHECKSTYLE-24?page=all ]
Lukas Theussl updated MPCHECKSTYLE-24:
--
Fix Version: 3.0.1
checktyle looks for headerFile in wrong directory when ran in multiproject
mode
[ http://jira.codehaus.org/browse/MAVEN-1626?page=comments#action_57767 ]
Lukas Theussl commented on MAVEN-1626:
--
Sorry Doug, but I _can_ reproduce it:
[EMAIL PROTECTED] MAVEN-1626]$ maven test-issue
__ __
| \/ |__ _Apache__
[ http://jira.codehaus.org/browse/MAVEN-1626?page=all ]
Lukas Theussl closed MAVEN-1626:
Resolution: Won't Fix
Fix Version: (was: 1.1-rc1)
We pinned this down to a namespace issue: you have to give a xmlns=dummy
attribute to the project
[ http://jira.codehaus.org/browse/MAVEN-1623?page=all ]
Lukas Theussl closed MAVEN-1623:
Resolution: Fixed
copyResources does not preservelastmodified
---
Key: MAVEN-1623
URL: http
[ http://jira.codehaus.org/browse/MAVEN-1708?page=all ]
Lukas Theussl closed MAVEN-1708:
Resolution: Fixed
NPE copying resources when no directory
---
Key: MAVEN-1708
URL: http
I wanted to ask you about that: shouldn't the directory element be
required in the pom? It is not with the current xsd. But if you want to
include resources in ${basedir}, one should at least include
directory${basedir}/directory.
Otherwise, how can I access the basedir property from a
just fine, you don't need to set it
to basedir).
I really thought I fixed this... maybe in Project.java?
Lukas Theussl wrote:
I wanted to ask you about that: shouldn't the directory element be
required in the pom? It is not with the current xsd. But if you want to
include resources in ${basedir
Ok, time's up and we have 4 binding +1 votes (Emmanuel, Arnaud, Vincent
M, Lukas) and 1 non-binding (Stephane who only put +0 on jira).
I will release this weekend (if I don't forget after the superbowl...)
Cheers,
Lukas
Lukas Theussl wrote:
Hi again,
I'd like to release the following m1
Hey Doug,
We are trying to update all the core plugins for inclusion in m11b3
first, see [1] for a status. But help on the core is certainly
appreciated, feel free to take any open issues that are scheduled for
11b3, if the count there is on zero, we'll cut a release.
Cheers,
Lukas
[1]
[ http://jira.codehaus.org/browse/MAVEN-1549?page=all ]
Lukas Theussl closed MAVEN-1549:
Resolution: Duplicate
Fix Version: (was: 1.1-beta-3)
Excution of pregoals twice.
---
Key: MAVEN-1549
[ http://jira.codehaus.org/browse/MAVEN-1729?page=all ]
Lukas Theussl closed MAVEN-1729:
Resolution: Incomplete
java.lang.NoClassDefFoundError
--
Key: MAVEN-1729
URL: http://jira.codehaus.org
[ http://jira.codehaus.org/browse/MAVEN-1734?page=all ]
Lukas Theussl closed MAVEN-1734:
Resolution: Incomplete
Provider org.apache.xerces.jaxp.SAXParserFactoryImpl could not be
instantiated: java.lang.NullPointerException
[ http://jira.codehaus.org/browse/MAVEN-1701?page=all ]
Lukas Theussl closed MAVEN-1701:
Resolution: Incomplete
NEON][JDBC] Can't load scjd12ts.dll, file not found, eventhough on system path
Stephane Nicoll wrote:
+1 for All except Jira-plugin +0 ; Dependency on Jira 3.3+ might be a
big issue. Had anyone sent a mail to the user list about it?
I don't think this is a big issue. The restriction to Jira 3.3+ was
necessary because of an API change in Jira itself, see
[ http://jira.codehaus.org/browse/MPPLUGIN-35?page=all ]
Lukas Theussl closed MPPLUGIN-35:
-
Resolution: Fixed
Now using ${maven.final.name}.jar everywhere. Plugins need standard names so
they can be uninstalled properly.
plugin:install fails
[ http://jira.codehaus.org/browse/MPJAVA-8?page=all ]
Lukas Theussl closed MPJAVA-8:
--
Resolution: Fixed
Closing now that MPPLUGIN-35 is fixed, I don't see any other place where this
is still an issue. The war case won't be fixed for backwards
[ http://jira.codehaus.org/browse/MPPLUGIN-30?page=all ]
Lukas Theussl updated MPPLUGIN-30:
--
Fix Version: 1.7.1
Can't we simply add a property to choose whether plugins get installed in
maven.plugin.dir or maven.plugin.user.dir?
Plugins on a per
[ http://jira.codehaus.org/browse/MPSCM-76?page=all ]
Lukas Theussl closed MPSCM-76:
--
Resolution: Fixed
Make scm plugin independent of release
--
Key: MPSCM-76
URL: http://jira.codehaus.org
Actually, pmd 3.5 has been released but it's not on ibiblio yet, see
http://jira.codehaus.org/browse/MPMD-12
-Lukas
[EMAIL PROTECTED] wrote:
Author: aheritier
Date: Tue Jan 31 08:53:29 2006
New Revision: 373872
URL: http://svn.apache.org/viewcvs?rev=373872view=rev
Log:
begin 1.8-SNAPSHOT
[ http://jira.codehaus.org/browse/MPCLOVER-39?page=all ]
Lukas Theussl closed MPCLOVER-39:
-
Resolution: Won't Fix
See comment above
Sources file should not be instrumented when no test file is present
[ http://jira.codehaus.org/browse/MPCLOVER-45?page=all ]
Lukas Theussl closed MPCLOVER-45:
-
Resolution: Fixed
Fix Version: 1.11
Allow specifying the relative property for clover-setup
[ http://jira.codehaus.org/browse/MPCLOVER-50?page=all ]
Lukas Theussl closed MPCLOVER-50:
-
Resolution: Fixed
Fix Version: 1.11
Add support for span
Key: MPCLOVER-50
URL: http://jira.codehaus.org
[ http://jira.codehaus.org/browse/MPDASHBOARD-28?page=all ]
Lukas Theussl closed MPDASHBOARD-28:
Resolution: Fixed
Fix Version: 1.9
Please sorth the report in alpha order
--
Key: MPDASHBOARD
Have a look at the file tag of the jelly core library:
http://jakarta.apache.org/commons/jelly/tags.html
There are lots of examples of its use in the maven plugins.
-Lukas
Nascif Abousalh-Neto wrote:
Hi,
I am trying to port the DTD removal code from an XML file (coverage.xml from
the
Hi again,
I'd like to release the following m1 plugins for inclusion in m11b3:
[] maven-checkstyle-plugin-3.0
[] maven-clover-plugin-1.11
[] maven-dashboard-plugin-1.9
[] maven-jdepend-plugin-1.6
[] maven-jira-plugin-1.3
Please check the changes and jira reports on the plugin web pages below
[ http://jira.codehaus.org/browse/MPARTIFACT-64?page=all ]
Lukas Theussl closed MPARTIFACT-64:
---
Resolution: Fixed
Fix Version: (was: 1.7.1)
1.8
Move create-upload-bundle goal from repository-plugin to artifact
[ http://jira.codehaus.org/browse/MPCLOVER-52?page=all ]
Lukas Theussl closed MPCLOVER-52:
-
Assign To: (was: Vincent Massol)
Resolution: Fixed
Upgrade to Clover 1.3.11
Key: MPCLOVER-52
URL
[ http://jira.codehaus.org/browse/MPDASHBOARD-33?page=all ]
Lukas Theussl closed MPDASHBOARD-33:
Resolution: Fixed
Will release checkstyle and dashboard together this week.
Change location of checkstyle files after releasing checkstyle plugin
[ http://jira.codehaus.org/browse/MPJIRA-10?page=all ]
Lukas Theussl closed MPJIRA-10:
---
Assign To: (was: Emmanuel Venisse)
Resolution: Fixed
Fix Version: 1.3
Using NTLM proxy
Key: MPJIRA-10
URL
[ http://jira.codehaus.org/browse/MPA-46?page=comments#action_57336 ]
Lukas Theussl commented on MPA-46:
--
I think a generic account Nobody or Unmaintained would be good.
Remove or change m1 plugins leaders
701 - 800 of 1441 matches
Mail list logo
