If you have renamed the file, where is your problem ? Using eclipse, you can easily refactor the code and it will change everything needed (at least in java files). I don' t how using ant will help you on that.
On 8/3/06, Soumadeep-Infravio <[EMAIL PROTECTED]> wrote:
Ok then for the time being, let me then follow the same dir structure and use ant to get things moving. Are you ok with that? Soumadeep ----- Original Message ----- From: "Guillaume Nodet" <[EMAIL PROTECTED]> To: <servicemix-dev@geronimo.apache.org> Sent: Thursday, August 03, 2006 7:15 PM Subject: Re: creating a standard JBI Component using servicemix-common module > Yeah, unfortunately, I don't think this is currently possible with maven > archetypes :( > Unless someone know a way to generate new files from velocity templates. > > On 8/3/06, Soumadeep-Infravio <[EMAIL PROTECTED]> wrote: >> >> Not a good idea to refactor the class names, like I said -> changing to >> BAMxxx, I think it's better to change the filenames in the template. The >> reason is there are a whole lot of xml and xsds which refer to the java >> classes... >> >> your thoughts.. >> >> Soumadeep >> ----- Original Message ----- >> From: "Soumadeep-Infravio" <[EMAIL PROTECTED]> >> To: <servicemix-dev@geronimo.apache.org> >> Sent: Thursday, August 03, 2006 6:08 PM >> Subject: Re: creating a standard JBI Component using servicemix-common >> module >> >> >> > Yup.. the classpath variable in Eclipse. I am changing the classes to >> > BAMxxx >> > >> > Thanks >> > Soumadeep >> > >> > ----- Original Message ----- >> > From: "Guillaume Nodet" <[EMAIL PROTECTED]> >> > To: <servicemix-dev@geronimo.apache.org> >> > Sent: Thursday, August 03, 2006 5:47 PM >> > Subject: Re: creating a standard JBI Component using servicemix-common >> > module >> > >> > >> >> Have you defined the property M2_REPO in Eclipse ? >> >> >> >> On 8/3/06, Soumadeep-Infravio <[EMAIL PROTECTED]> wrote: >> >>> >> >>> Resolved it... problem with classpath. >> >>> >> >>> It created two eclipse related files >> >>> 1) .project >> >>> 2) .classpath >> >>> >> >>> The problem is when I import this project into Eclipse it doesn't >> >>> resolve >> >>> the classapth. >> >>> Do I need to do anything else? >> >>> >> >>> Thanks >> >>> Soumadeep >> >>> >> >>> >> >>> ----- Original Message ----- >> >>> From: "Guillaume Nodet" <[EMAIL PROTECTED]> >> >>> To: <servicemix-dev@geronimo.apache.org> >> >>> Sent: Thursday, August 03, 2006 3:11 PM >> >>> Subject: Re: creating a standard JBI Component using >> >>> servicemix-common >> >>> module >> >>> >> >>> >> >>> > What do you mean by not OK ? >> >>> > >> >>> > On 8/3/06, Soumadeep-Infravio <[EMAIL PROTECTED]> wrote: >> >>> >> >> >>> >> Guillaume, >> >>> >> >> >>> >> I guess I got past this by re-building smx. What I am stuck with >> now >> >>> >> is >> >>> >> that >> >>> >> eclipse is complaining that the project that was created using the >> >>> >> command >> >>> >> mvn eclipse:eclipse is not OK. >> >>> >> >> >>> >> Have you tried doing it lately? >> >>> >> >> >>> >> Thanks >> >>> >> Soumadeep >> >>> >> >> >>> >> ----- Original Message ----- >> >>> >> From: "Guillaume Nodet" <[EMAIL PROTECTED]> >> >>> >> To: <servicemix-dev@geronimo.apache.org> >> >>> >> Sent: Thursday, August 03, 2006 2:40 PM >> >>> >> Subject: Re: creating a standard JBI Component using >> >>> >> servicemix-common >> >>> >> module >> >>> >> >> >>> >> >> >>> >> > You can also download the archetype from >> >>> >> > >> >>> >> > >> >>> >> >> >>> >> http://people.apache.org/maven-snapshot-repository/org/apache/servicemix/tooling/servicemix-service-engine/1.0-incubating-SNAPSHOT/servicemix-service-engine-1.0-incubating-20060803.064327-5.jar >> >>> >> > and put it in your local maven repo under >> >>> >> > >> >>> >> > >> >>> >> >> >>> >> ~/.m2/org/apache/servicemix/tooling/servicemix-service-engine/1.0-incubating-SNAPSHOT >> >>> >> > It should also work. >> >>> >> > >> >>> >> > On 8/3/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote: >> >>> >> >> >> >>> >> >> We currently have problems uploading snapshots. >> >>> >> >> Even in this case, as they are not on public repositories, I'm >> not >> >>> >> >> sure it would work. >> >>> >> >> The best way would be to build ServiceMix from sources, as >> >>> >> >> the archetypes will be in your local repository. >> >>> >> >> >> >>> >> >> >> >>> >> >> On 8/3/06, vikas kumar <[EMAIL PROTECTED]> wrote: >> >>> >> >> > >> >>> >> >> > Hi Guillaume/All, >> >>> >> >> > >> >>> >> >> > Tried creating a standard JBI Component using >> servicemix-common >> >>> >> module. >> >>> >> >> > I followed the steps written in >> >>> >> >> > >> http://servicemix.org/site/creating-a-standard-jbi-component.html >> >>> >> >> > >> >>> >> >> > On executing the command >> >>> >> >> > >> >>> >> >> > mvn archetype:create \ >> >>> >> >> > -DarchetypeGroupId=org.apache.servicemix.tooling \ >> >>> >> >> > -DarchetypeArtifactId=servicemix-service-engine \ >> >>> >> >> > -DarchetypeVersion=1.0-incubating-SNAPSHOT \ >> >>> >> >> > -DgroupId=org.apache.servicemix.xslt \ >> >>> >> >> > -DartifactId=servicemix-xslt >> >>> >> >> > >> >>> >> >> > I got the following error: >> >>> >> >> > >> >>> >> >> > [ERROR] ResourceManager : unable to find resource >> >>> >> >> > 'VM_global_library.vm' >> >>> >> >> > in any >> >>> >> >> > resource loader. >> >>> >> >> > [INFO] Velocimacro : error using VM library template >> >>> >> >> > VM_global_library.vm : org >> >>> >> >> > .apache.velocity.exception.ResourceNotFoundException: Unable >> to >> >>> find >> >>> >> >> > resource 'V >> >>> >> >> > M_global_library.vm' >> >>> >> >> > [INFO] Velocimacro : VM library template macro registration >> >>> >> complete. >> >>> >> >> > [INFO] Velocimacro : allowInline = true : VMs can be defined >> >>> inline >> >>> >> in >> >>> >> >> > templates >> >>> >> >> > >> >>> >> >> > [INFO] Velocimacro : allowInlineToOverride = false : VMs >> defined >> >>> >> inline >> >>> >> >> > may NOT >> >>> >> >> > replace previous VM definitions >> >>> >> >> > [INFO] Velocimacro : allowInlineLocal = false : VMs defined >> >>> >> >> > inline >> >>> >> will >> >>> >> >> > be glob >> >>> >> >> > al in scope if allowed. >> >>> >> >> > [INFO] Velocimacro : initialization complete. >> >>> >> >> > [INFO] Velocity successfully started. >> >>> >> >> > [INFO] [archetype:create] >> >>> >> >> > [INFO] Defaulting package to group ID: >> org.apache.servicemix.bam >> >>> >> >> > [INFO] >> >>> >> >> > >> >>> >> >> >>> >> ------------------------------------------------------------------------ >> >>> >> >> > [ERROR] BUILD ERROR >> >>> >> >> > [INFO] >> >>> >> >> > >> >>> >> >> >>> >> ------------------------------------------------------------------------ >> >>> >> >> > [INFO] Failed to resolve artifact. >> >>> >> >> > >> >>> >> >> > GroupId: org.apache.servicemix.tooling >> >>> >> >> > ArtifactId: servicemix-service-engine >> >>> >> >> > Version: 1.0-incubating-SNAPSHOT >> >>> >> >> > >> >>> >> >> > Reason: Unable to download the artifact from any repository >> >>> >> >> > >> >>> >> >> > Try downloading the file manually from the project website. >> >>> >> >> > >> >>> >> >> > Then, install it using the command: >> >>> >> >> > mvn install:install-file -DgroupId= >> >>> >> >> > org.apache.servicemix.tooling-DartifactI >> >>> >> >> > d=servicemix-service-engine \ >> >>> >> >> > -Dversion=1.0-incubating-SNAPSHOT -Dpackaging=jar >> >>> >> >> > -Dfile=/path/to/file >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> >>> >> org.apache.servicemix.tooling:servicemix-service-engine:jar:1.0-incubating-SNA >> >>> >> >> > PSHOT >> >>> >> >> > >> >>> >> >> > from the specified remote repositories: >> >>> >> >> > central (http://repo1.maven.org/maven2) >> >>> >> >> > >> >>> >> >> > Any pointers? >> >>> >> >> > >> >>> >> >> > ~Vikas >> >>> >> >> > >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> -- >> >>> >> >> Cheers, >> >>> >> >> Guillaume Nodet >> >>> >> >> >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > -- >> >>> >> > Cheers, >> >>> >> > Guillaume Nodet >> >>> >> > >> >>> >> >> >>> >> >> >>> >> >> >>> > >> >>> > >> >>> > -- >> >>> > Cheers, >> >>> > Guillaume Nodet >> >>> > >> >>> >> >>> >> >>> >> >> >> >> >> >> -- >> >> Cheers, >> >> Guillaume Nodet >> >> >> > >> > >> > >> >> >> > > > -- > Cheers, > Guillaume Nodet >
-- Cheers, Guillaume Nodet
