Forgot to send it to [EMAIL PROTECTED] 2007-02-14 (수), 18:50 +0900, Trustin Lee 쓰시길: > Hi John, > > 2007-02-09 (금), 11:18 -0600, John E. Conlon 쓰시길: > > I broke the mina core build the other day by adding a plugin to the > > project but without specifying a version for the plugin. Sorry, if I > > would have removed my local repo and tested again I would have saw my > > error. :-[ > > It's OK. :) > > > Just committed that fix and re-enabled the plugin, (and it did test good > > this time) ... but in order not to break portability for the mina core > > project again, I want to confirm the conventions for specifying plugin > > repos for Mina. > > > > Do we expect mina builders as a convention to specify the pluginRepos in > > their settings.xml like - > > > > <pluginRepository> > > <id>apache.snapshots</id> > > <name>Apache Snapshot Plugin Repository</name> > > <url>http://people.apache.org/repo/m2-snapshot-repository</url> > > <releases> > > <enabled>false</enabled> > > </releases> > > <snapshots> > > <enabled>true</enabled> > > </snapshots> > > </pluginRepository> > > </pluginRepositories> > > > > If this convention is not expected of mina builders then we will need to > > add this specification to the parent pom.xml in the base trunk directory > > in order to find the apache felix plugin that is now reactivated. > > I'd rather add this specification to the parent pom.xml because it's > makes other people's life much easier. People will think our build is > broken because it doesn't work as long as he or she doesn't modify the > settings.xml. Let me try to add it to the parent pom. > > Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
signature.asc
Description: This is a digitally signed message part
