https://issues.jboss.org/browse/SEAMFORGE-142

On Mon, Apr 18, 2011 at 3:37 PM, Dan Allen <dan.j.allen@gmail.com> wrote:
Is there an issue report? If so, we can shop it around the twitter-sphere. Sounds like a good opportunity for a newcomer to tackle, as ALR likes to emphasize.

-Dan


On Mon, Apr 18, 2011 at 20:23, Lincoln Baxter, III <lincolnbaxter@gmail.com> wrote:
Yeah, definitely come to the conclusion that this needs to be supported; however, it will have to wait until after JBW unless someone else wants to take a stab :)


On Mon, Apr 18, 2011 at 1:25 PM, Dan Allen <dan.j.allen@gmail.com> wrote:
On Mon, Apr 18, 2011 at 13:23, Dan Allen <dan.j.allen@gmail.com> wrote:
On Sat, Apr 2, 2011 at 18:24, Lincoln Baxter, III <lincolnbaxter@gmail.com> wrote:
As far as classifiers. I've been intentionally avoiding them because it adds a lot of complexity to the dependency API. What do you need?

Regardless of whether you like classifiers in general, you can't ignore the fact that they are part of a dependency. You really need to support them or else the forge dep support is just incomplete.

I agree that they are bad for distinguishing between two artifacts (like in the case of testng). The main intention for them is to reference complementary jars, like -source, -javadoc, etc. Of course, you don't need to add those as dependencies.

-Dan

--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597





--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"



--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597





--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"