Which version of site-plugin-2.x are you comparing with? I would expect
2.3 to be equivalent with 3.0.
-Lukas
Simone Tripodi wrote:
Hi all guys,
while redeploying the Cocoon3 site, using mvn3+site-plugin:3.0, I
noticed a big difference in the generated page using
mvn2+site-plugin:2.X,
I've tried it out on a few relatively tame builds...failsafe and
dependency plugins being about the most exotic things tested.
Everything looks like it's functioning well here. I'll try to take it
out for a more aggressive test run today.
On 12/5/11 9:28 AM, Olivier Lamy wrote:
Hello,
FYI - NetBeans nightly development builds [1] are now bundling RC3, to shake
out problems in either the embedded APIs or general usage.
[1] http://bits.netbeans.org/download/trunk/nightly/latest/
-
To unsubscribe, e-mail:
Hi Simone,
there are still a few issues in Jira left, which I can pick up.
Next I'll have to verify that all issues of reskinning a site are covered.
One thing I'm missing is IT-verifications, something which can check values of
attributes or tags. For instance: are the width and height of
Jesse,
First huge thanks for your tests, that's very important for us to have
feedbacks.
But please note it's *not* an official release so this will never be
distribute as an official Apache Maven release.
It's only a rc build to get feedbacks from users. The staged
repository will be deleted (at
FWIW, 3.0.4-RC3 didn't worked with a custom repository layout
Like
http://kthoms.wordpress.com/2009/10/13/how-to-register-a-custom-maven-repository-layout/
I did not pin down the problem yet, but seems a regression from 3.0.3.
On Mon, Dec 5, 2011 at 12:28 PM, Olivier Lamy ol...@apache.org
Hello,
I see, that mojo regularly uses groovy scripts for the verifiy step in
integration tests of plugins. However maven plugins seem to use bsh,
which is a pain compared to groovy. Are maven-plugins not allowed to
use groovy for these tests?
Regards Mirko
--
2011/12/7 Mirko Friedenhagen mfriedenha...@gmail.com:
Hello,
I see, that mojo regularly uses groovy scripts for the verifiy step in
integration tests of plugins. However maven plugins seem to use bsh,
which is a pain compared to groovy. Are maven-plugins not allowed to
use groovy for these
2011/12/7 Marvin Froeder velo...@gmail.com:
FWIW, 3.0.4-RC3 didn't worked with a custom repository layout
Like
http://kthoms.wordpress.com/2009/10/13/how-to-register-a-custom-maven-repository-layout/
I did not pin down the problem yet, but seems a regression from 3.0.3.
How do you get that
Code in a plugin at CXF calls artifactResolver.resolve(artifact,
remoteRepos, localRepository) and gets an impossible answer (the
'classes' directory when the artifact in question is of type 'wsdl').
Where does this live? All the way over at Eclipse, or somewhere else?
In terms of reporting, if it doesn't work in Maven, it goes in MNG, regardless
of where the code at fault might be... whoever comes to fix it may need to file
a bug with Aether too, but at first glance that looks like something that's
within Maven code.
- Brett
On 08/12/2011, at 10:19 AM,
On 12/07/2011 02:04 PM, Olivier Lamy wrote:
please note it's *not* an official release so this will never be
distribute as an official Apache Maven release.
It's only a rc build to get feedbacks from users.
Yes of course. This is only temporary until another RC or a final build is
published -
Are you running inside m2e by any chance?
--
Regards,
Igor
On 11-12-07 6:19 PM, Benson Margulies wrote:
Code in a plugin at CXF calls artifactResolver.resolve(artifact,
remoteRepos, localRepository) and gets an impossible answer (the
'classes' directory when the artifact in question is of type
I'm +1ing this - have been doing releases all day without issue.
Someone did make a comment about memory usage the other day, I am seeing
OOM exceptions more often in my large reactor build under the RC, but
that's mostly Rhino stuff that has an evil leak in it.
I did see a Permgen in Javac
MSITE-623 describes the situation, but, in fact, it's not MSITE at all.
In the case at hand, the artifact resolver is returning the current
target/classes pathname that goes with the 'jar' artifact as the
answer to a question about the 'wsdl' artifact. Maven 2.2.1 does fine.
Where do I start?
Hello Robert!
thanks for your enthusiasm on fluido! :) About the searchbar on top, I
would like to reach that[1] rendering - I'll try to work on it
tomorrow (today I'm off for the bigger part of the day)
Thanks again!
Simo
[1] http://imageshack.us/f/17/screenshot20111208at848.png/
16 matches
Mail list logo
