Extra in Maven report
-
Key: MJNCSS-52
URL: https://jira.codehaus.org/browse/MJNCSS-52
Project: Maven 2.x JavaNCSS Plugin
Issue Type: Bug
Affects Versions: 2.0
Environment: Windows 7
Maven 3
Java 6
Each git repository has a pom.xml at the root level, and each repo
contains the subject of one release only. I think the internal
structure of the git repo is
not really anything that needs to be discussed. The "external" view is
mostly of which url we put up on a webpage, and I think Paul's co
The convention "group/project-repo" seems to be followed on other sites
as well.
http://git.kernel.org/
On 06/23/2011 08:14 PM, Paul Gier wrote:
> Not sure I understand you. I wasn't saying we should have a single git
> repo, I was suggesting that each plugin/project is located in it's own
> git
Not sure I understand you. I wasn't saying we should have a single git
repo, I was suggesting that each plugin/project is located in it's own
git repo under the common directory "mojo". Instead of prefixing the
name of the repo with "mojo-". Either way there is one git repo per
mojo project. Th
until you try to release.
if you release separately, you need separate git repositories.
if you release at the same time, same git repo.
so animal-sniffer would be one repo for the tools, one repo for each of the
signatures.
- Stephen
---
Sent from my Android phone, so random spelling mistakes
I think I would prefer a directory called "mojo".
So "mojo/gwt-maven-plugin.git" instead of "mojo-gwt-maven-plugin.git"
WDYT?
On 06/23/2011 04:37 PM, Robert Scholte wrote:
> Looking at http://git.codehaus.org/gitweb.cgi it looks to me we want
> something like jbehave has done.
> In our case that w
Looking at http://git.codehaus.org/gitweb.cgi it looks to me we want something
like jbehave has done.
In our case that would mean something like "mojo-gwt-maven-plugin.git" or
"mojo-gwtmavenplugin" or...
our /trunk/mojo has 89 projects, I'm not sure if we have to do some cleanup
here (could be
[
https://jira.codehaus.org/browse/MTAGLIST-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271214#comment-271214
]
Alix Lourme commented on MTAGLIST-56:
-
For information, patch used on many projects in company
+1 for moving to git - much easier to work with remotely.
+1 for moving each mojo to its own git repo
On the latter point, you *need* to do this. Anything that potentially requires
its own tag or branch needs its own git repo.
Kind regards,
Christopher
--
Make sonar-maven-plugin thread-safe for maven 3
---
Key: MOJO-1697
URL: https://jira.codehaus.org/browse/MOJO-1697
Project: Mojo
Issue Type: Improvement
Components: sonar
Affects Vers
FYI.
SNAPSHOT with rc3 deployed.
fix ff5 support.
2011/6/22 Olivier Lamy :
> Cool !
> FYI I will upgrade to rc3.
> And probably release it soon (or wait the final 2.0 depends if it's long)
>
>
> 2011/6/22 Greg Akins :
>> On Tue, Jun 21, 2011 at 10:56 AM, Olivier Lamy wrote:
>>> Hello,
>>> http://
[
https://jira.codehaus.org/browse/MGWT-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof reassigned MGWT-301:
Assignee: nicolas de loof
> The plugin is too sensitive to changes in unrelated parts of a project
[
https://jira.codehaus.org/browse/MGWT-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-301.
Resolution: Fixed
Fix Version/s: 2.3.0-1
patch applied
> The plugin is too sensitive to changes in
In general, I think the mojo project is happy to accept any new plugins
as long as they don't duplicate/conflict with what we already have. So
your plugins sound fine to submit. The difficult part is usually
getting someone to take the time to review it and work on it. Do you
see a path for merg
The plugin is too sensitive to changes in unrelated parts of a project,
rebuilding unnecessarily
Key: MGWT-301
URL: https://jira.codehaus.org/browse/MGWT-301
>
>
>>
>> I am a bit unsure as to what is the expected gain wrt moving the
> /authorative/ repo to github. I've said this earlier;
> an authorative repo located at codehaus with mirroring to github is
> practically the same. Handling pull requests is the only
> difference I can think of but it sho
Den 23.06.2011 14:48, skrev nicolas de loof:
2011/6/23 Mark Struberg
generally I'm
+1 for moving the repos from SVN to GIT
-1 for moving the repo from codehaus.org to github.
Reason is that this would _heavily_ fragment this established community.
Why not just setup a GIT repo at codehaus?
2011/6/23 Mark Struberg
> generally I'm
>
> +1 for moving the repos from SVN to GIT
>
> -1 for moving the repo from codehaus.org to github.
> Reason is that this would _heavily_ fragment this established community.
> Why not just setup a GIT repo at codehaus? This is pretty easy, I could
> volu
generally I'm
+1 for moving the repos from SVN to GIT
-1 for moving the repo from codehaus.org to github.
Reason is that this would _heavily_ fragment this established community. Why
not just setup a GIT repo at codehaus? This is pretty easy, I could volunteer
on that.
@Lee Thompson regar
2011/6/23 Arnaud Héritier :
> Myself I'm not at all in favor to migrate to one Git repo which could be the
> case which requires such feature.
I haven't got much experience with Git. Basically, I'm all in favour
for the ability to check out a single Mojo and work on that.
OTOH: Does that leave u
[
https://jira.codehaus.org/browse/MFINDBUGS-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Todorov updated MFINDBUGS-144:
-
Attachment: usage.apt.vm.diff
Attached a diff for the fix.
> Usage page has syntax errors
Usage page has syntax errors in the examples
Key: MFINDBUGS-144
URL: https://jira.codehaus.org/browse/MFINDBUGS-144
Project: Maven 2.x FindBugs Plugin
Issue Type: Bug
Affects Versions: 2.3.2
I'm back
Sorry for the delay
Myself I'm not at all in favor to migrate to one Git repo which could be the
case which requires such feature.
I think we need to split/convert our SVN in many Git repositories, one per
plugin
Thus it is less easy than just converting a svn with trunk/tags/branches
in
+1 Great!
-fotos
On Wed, Jun 22, 2011 at 23:22, Robert Scholte wrote:
> Hi,
>
> I'd like to release version 1.6 of the build-helper-maven-plugin
>
> This plugin contains various small independent goals to assist with the
> Maven build lifecycle.
>
> We solved 5 issues:
> http://jira.codehaus.org
On Wed, 22 Jun 2011 20:22:55 +
Robert Scholte wrote:
+1
Well done :)
>
> Hi,
>
> I'd like to release version 1.6 of the build-helper-maven-plugin
>
> This plugin contains various small independent goals to assist with
> the Maven build lifecycle. We solved 5 issues:
> http://jira.codehaus.
+1
2011/6/22 Robert Scholte :
> Hi,
>
> I'd like to release version 1.6 of the build-helper-maven-plugin
>
> This plugin contains various small independent goals to assist with the
> Maven build lifecycle.
>
> We solved 5 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11702&v
26 matches
Mail list logo
