Only the history is wrong AFAICT. Actually I just checked that there are
two bogus commits in each of the plugins you mentioned (antrun, ejb,
linkcheck, pdf).
In each case there was no net code change AFAICT, only the two commit
logs could be confusing, eg for the antrun plugin, there are no
When you say that something is wrong with the PDF plugin, do you mean it
won't build, or do you mean the SVN history is wrong? I'm not sure how
to fix the SVN history; this apparently happened inadvertently when I
dcommit'ed from my git repository (since ASF is sync'ing the entire
maven-plugins
Brett Porter wrote:
On 21/09/2010, at 11:49 PM, Lukas Theussl wrote:
Hi John,
There is something wrong in the pdf plugin: the last two commit logs are
duplicated with you as author [1], however no commits happened apparently. Can
you check that?
Actually, r999592 seems to have reverted
On 21/09/2010, at 11:49 PM, Lukas Theussl wrote:
>
> Hi John,
>
> There is something wrong in the pdf plugin: the last two commit logs are
> duplicated with you as author [1], however no commits happened apparently.
> Can you check that?
Actually, r999592 seems to have reverted to the less c
Hi John,
There is something wrong in the pdf plugin: the last two commit logs are
duplicated with you as author [1], however no commits happened
apparently. Can you check that?
Thanks,
-Lukas
[1]
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-pdf-plugin/src/main/java/org/apache/ma
It seems that there were no net changes after this series of commits.
There were some new revisions applied to the following plugins:
- ejb
- linkcheck
- pdf
- antrun
If you find any problems related to these plugins, let me know and I'll
be happy to address them.
-john
On 9/21/10 4:37 PM,
I've been working on the next version of the maven-assembly-plugin by
using the ASF github location for maven-plugins. I got several commits
queued up, did a `git svn rebase` and followed that with a `git svn
dcommit`. Now, it looks like there may be a lot of collateral damage to
other plugins.
