Oops, wrong mailing list. Sorry.
Jérémie
2011/7/24 Jérémie
> Hi,
>
> I would like to release the first version (0.1) of Drools Sonar Plugin.
>
> This version requires sonar 2.2+
>
> *5 issues has been solved.*
> http://jira.codehaus.org/browse/SONARPLUGINS/fixforversion/17498
>
> *Download *(s
fixforversion/17498<http://jira.codehaus.org/browse/SONARPLUGINS/fixforversion/17498>
>
> Download (snapshot)
> http://snapshots.repository.**codehaus.org/org/codehaus/**
> sonar-plugins/sonar-drools-**plugin/0.1-SNAPSHOT/sonar-**
> drools-plugin-0.1-20110724.**170524-1.jar<http://snap
ok, I added a doc to add a protocol and improved the error message [1]
I think we can safely do the change proposed in MSITE-598: users won't be lost
(of course, they'll need to read the error message...)
Regards,
Hervé
[1] http://jira.codehaus.org/browse/MSITE-599
Le dimanche 24 juillet 2011
A thought: since 'extensions' has no 'management' or inheritance
control, the use of it is actually harder and more obscure when people
want to use other versions. It's far easier to just manage
dependencies of the site plugin via pluginManagement. So, I'm in favor
of using and documenting dependen
Hi,
I would like to release the first version (0.1) of Drools Sonar Plugin.
This version requires sonar 2.2+
5 issues has been solved.
http://jira.codehaus.org/browse/SONARPLUGINS/fixforversion/17498
Download (snapshot)
http://snapshots.repository.codehaus.org/org/codehaus/sonar-plugins/sonar
I've already made a jira-issue for it, MSITE-598 [1]. I think we should stay
consistent: specify wagons with extensions.We just need to document this very
well, both on the site and the failure-message, including the required xml to
add to the pom. -Robert [1] http://jira.codehaus.org/browse/MS
Hi,
I would like to release the first version (0.1) of Drools Sonar Plugin.
This version requires sonar 2.2+
*5 issues has been solved.*
http://jira.codehaus.org/browse/SONARPLUGINS/fixforversion/17498
*Download *(snapshot)
http://snapshots.repository.codehaus.org/org/codehaus/sonar-plugins/so
one last decision/documentation point about m-site-p 3 with Maven 3
we had a discussion on IRC yesterday with Robert, Mark and Benjamin about
wagon and its change in M3 [1].
It was about the way we promote configuring wagon protocols in plugins:
- in m-deploy-p, we promote using extensions (and
Since I can't edit the Wiki, I created:
https://docs.google.com/document/d/1k3E4vx_4cKJ4zzksVM4oROX3Dffsh0Q4VOGVjd3oUto/edit?hl=en_US
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev
Hi, thanks for the feedback. I've adjusted the page a bit.For most of them I
agree, but I think we should tell something about environment tooling. Maybe as
some kind of wiki-text while explaining the features of Maven. Another approach
is to ask yourself the following questions and give it a p
10 matches
Mail list logo