I assumed it was because it isn't a bundle so it doesn't need an artifactId that works as bundle-symbolic-name. I find the different naming handy to remind me that it isn't a bundle.
david jencks On Nov 15, 2011, at 8:44 AM, Daniel Kulp wrote: > > Is there any reason why blueprint-parser doesn't use an artifactId that > matches the rest of the aries blueprint artifactIds? Is that something we > can change without breaking anything major? > > -- > Daniel Kulp > [email protected] > http://dankulp.com/blog > Talend - http://www.talend.com
