[jbosside-dev] Re: jBPM Designer feature.xml needs to be updated

[Koen Aers]

No I meant actually to CC jbosside-dev :-))


________________________________

	From: marshall.jboss at gmail.com [mailto:marshall.jboss at gmail.com]
On Behalf Of Marshall Culpepper
	Sent: donderdag 14 september 2006 19:16
	To: Dev - JBoss IDE
	Subject: Fwd: [jbosside-dev] Re: jBPM Designer feature.xml needs
to be updated
	
	
	I think you meant to CC dev-jbosside on this one
	
	---------- Forwarded message ----------
	From: Koen Aers <koen.aers at jboss.com >
	Date: Sep 14, 2006 6:59 AM
	Subject: RE: [jbosside-dev] Re: jBPM Designer feature.xml needs
to be updated
	To: Marshall Culpepper <marshall.culpepper at jboss.com >
	
	
	I am pretty much OK with doing things the way they should be
done, no problem with that. 
	Btw, are you talking about the meeting when I was in India? I
cannot remember discussing this, but this might be due to some kind of
jetlag ;-). Anyway, we are in the process of releasing jBPM 3.2 alpha1
so the release has my number one attention at present. And as I
mentioned earlier, the good way to reuse the tag that Marshall has
written would be to bundle it in a library that resides in the
repository to avoid duplication. Or am I wrong about this?
	 
	Regards,
	Koen


________________________________

		
		
		From: marshall.jboss at gmail.com
[mailto:marshall.jboss at gmail.com] On Behalf Of Marshall Culpepper
		
		Sent: woensdag 13 september 2006 22:31
		To: Max Andersen
		Cc: Koen Aers; jbosside-dev at lists.jboss.org
		Subject: Re: [jbosside-dev] Re: jBPM Designer
feature.xml needs to be updated
		
		

	
	Yes, this is what we decided on our meeting.. we are moving all
dependencies to be included the "right" way, and retrofitting the build
system to calculate feature dependencies based on those entries, instead
of counting on eclipse PDE to auto-bundle things that are listed as
<plugin>. 
	
	
	On 9/13/06, Max Rydahl Andersen <max.andersen at jboss.com> wrote:
	

		just to be clear:
		
		Our old/current way of bundling things are *wrong* in
context of
		integrating with the rest of
		the eclipse ecosystem. you should only have <plugin> for
plugins that is
		actually part of the plugin 
		everything else is <import> of either plugin's or
feature's.
		
		
		


	-- 
	
	Marshall Culpepper
	marshall.culpepper at jboss.com
	JBossIDE Team Lead 
	JBoss, a division of Red Hat 


	-- 
	Marshall Culpepper
	marshall.culpepper at jboss.com
	JBossIDE Team Lead
	JBoss, a division of Red Hat 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20060914/6f97f1f4/attachment.html