You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by flmaven <jo...@hotmail.com> on 2013/08/05 18:17:17 UTC

"Unmaving" a project

Hello,
English is not my native language; please excuse typing errors.
I need to "unmave" a project because in the place I work Maven is not used.
The problem is that I downloaded a lot of source-code from a book and all
it´s content are Maven Projects.
I found easy to make the projects work as Maven Projects... just import a
Maven Project, configure my application server - I am using Jboss 7.0, and
run them. I could easily configure this projects after testing it and change
them to my needs. 
But since we don´t use Maven here, I started trying to disable the Maven
nature of a project and I couldn´t get the project to work. I deleted the
pom.xml file and added the libs that were necessary to the project classpath
- after clicking in the Eclipse IDE to disable Maven nature.
Is there any other configuration needed? When I want to "unmaven" project,
in addition to the libs, what should I pay attention?
Thanks for your attention.



--
View this message in context: http://maven.40175.n5.nabble.com/Unmaving-a-project-tp5766830.html
Sent from the Maven - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: "Unmaving" a project

Posted by flmaven <jo...@hotmail.com>.
I belive you are right, Wayne.
Thanks everybody for the replies.



--
View this message in context: http://maven.40175.n5.nabble.com/Unmaving-a-project-tp5766830p5766985.html
Sent from the Maven - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: "Unmaving" a project

Posted by Wayne Fay <wa...@gmail.com>.
> the errors one at a time. " - that´s what I am doing right now. I came here,
> because I thought it was a Maven related problem - since the project was the

This is not a general, all-purpose Java "fix it" forum. By simply
stating "I am not using Maven" we can tell you immediately that we're
almost certainly the wrong place to ask your questions.

> I am using Jboss 7.1 and the error seems to be related to a beams.xml file,
...
> This project is a JSF application using several CDI beans and an Activiti

I think you will have better luck (and a better reception) asking
these questions at the Java Ranch or some forums @ Oracle etc as your
problems seem to be specific to JSF and CDI.

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: "Unmaving" a project

Posted by flmaven <jo...@hotmail.com>.
The validation of the source is all right - no red X´s. The Java Build Path
is set correctly.
When running in the application server is where I can see the errors. I
cleaned the project.

"If that does not work, start engaging on the Eclipse forum to get rid of 
the errors one at a time. " - that´s what I am doing right now. I came here,
because I thought it was a Maven related problem - since the project was the
same and it was working before. Now I am reading the log and trying to
figure out.

I am using Jboss 7.1 and the error seems to be related to a beams.xml file,
in its loading or compilation... I am doing some research to understand it
better. 
This project is a JSF application using several CDI beans and an Activiti
process
definition.

I am attaching the log, if anyone has a clue, please give me a hint.

Thanks for your help.


error2.txt <http://maven.40175.n5.nabble.com/file/n5766976/error2.txt>  


Ron Wheeler wrote
> What exactly is the "not working" symptom?
> Can Eclipse do the validation of the source in the editor or is your 
> window full of red X's?
> 
> Does it compile? What errors do you get?
> 
> Are the project "Java Build Path" libraries, etc. set correctly.
> 
> Project ->Clean can sometimes help.
> 
> You really now have an Eclipse problem since Maven is no longer involved.
> You should probably be checking your project preferences with one of 
> your coworkers to see where your setup is different.
> If that does not work, start engaging on the Eclipse forum to get rid of 
> the errors one at a time.
> 
> 
> Ron
> 
> 
> On 06/08/2013 1:49 PM, Adrien Rivard wrote:
>> You should probably delete all  the eclipse files (.project .classpath,
>> .settings/* ) and recreate a new java project and eventually edit it to
>> match the maven project structure (src/main/java ...).
>>
>>
>>
>>
>> On Tue, Aug 6, 2013 at 7:29 PM, flmaven &lt;

> joao.ptv@

> &gt; wrote:
>>
>>> Hello Ron,
>>> Thanks for your reply.
>>> Where I work there is no use of scripts for creating projects. There is
>>> a
>>> base model that is used to create projects, but is not based on Maven,
>>> or
>>> Ant, it was created by the company.
>>> There is a "standard way", but this is not I am worried about.
>>> Right now, I am just worried with having a project without Maven that
>>> "would
>>> do" the same as the Maven project "would do".
>>> And this is what I am not understanding. I disabled the Maven nature of
>>> the
>>> project, added all the jars that where necessary to the project, and it
>>> won´t work.
>>> That´s why I asked if there were other necessary steps to make besides
>>> disable the Maven nature of the project and add the libs.
>>> Is there other points that I should pay attention when I disable the
>>> Maven
>>> nature of a project? What are they?
>>> Thanks for your attention.
>>>
>>>
>>> Ron Wheeler wrote
>>>> You probably need to start by finding out how everyone at your
>>>> organization builds projects.
>>>> For example, do they use a set of Ant scripts?
>>>>
>>>> Maven gives you a standard way to do things but if your organization is
>>>> not using Maven, it probably has a "standard" way that all of the
>>>> projects are built.
>>>> You may also need to restructure your source tree to match the
>>>> organization's way of organizing a project.
>>>>
>>>> I can not think of any reason why it would be necessary to remove the
>>>> pom.xml or tell Eclipse anything after you have removed the Maven
>>>> nature.
>>>>
>>>> No one here can tell you how your organization builds its applications
>>>> and that is what you need to find out.
>>>>
>>>> Ron
>>>>
>>>> On 05/08/2013 12:17 PM, flmaven wrote:
>>>>> Hello,
>>>>> English is not my native language; please excuse typing errors.
>>>>> I need to "unmave" a project because in the place I work Maven is not
>>>>> used.
>>>>> The problem is that I downloaded a lot of source-code from a book and
>>> all
>>>>> it´s content are Maven Projects.
>>>>> I found easy to make the projects work as Maven Projects... just
>>>>> import
>>> a
>>>>> Maven Project, configure my application server - I am using Jboss 7.0,
>>>>> and
>>>>> run them. I could easily configure this projects after testing it and
>>>>> change
>>>>> them to my needs.
>>>>> But since we don´t use Maven here, I started trying to disable the
>>>>> Maven
>>>>> nature of a project and I couldn´t get the project to work. I deleted
>>> the
>>>>> pom.xml file and added the libs that were necessary to the project
>>>>> classpath
>>>>> - after clicking in the Eclipse IDE to disable Maven nature.
>>>>> Is there any other configuration needed? When I want to "unmaven"
>>>>> project,
>>>>> in addition to the libs, what should I pay attention?
>>>>> Thanks for your attention.
>>>>>
>>>>>
>>
> 
> 
> -- 
> Ron Wheeler
> President
> Artifact Software Inc
> email: 

> rwheeler@

> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: http://maven.40175.n5.nabble.com/Unmaving-a-project-tp5766830p5766976.html
Sent from the Maven - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: "Unmaving" a project

Posted by Ron Wheeler <rw...@artifact-software.com>.
What exactly is the "not working" symptom?
Can Eclipse do the validation of the source in the editor or is your 
window full of red X's?

Does it compile? What errors do you get?

Are the project "Java Build Path" libraries, etc. set correctly.

Project ->Clean can sometimes help.

You really now have an Eclipse problem since Maven is no longer involved.
You should probably be checking your project preferences with one of 
your coworkers to see where your setup is different.
If that does not work, start engaging on the Eclipse forum to get rid of 
the errors one at a time.


Ron


On 06/08/2013 1:49 PM, Adrien Rivard wrote:
> You should probably delete all  the eclipse files (.project .classpath,
> .settings/* ) and recreate a new java project and eventually edit it to
> match the maven project structure (src/main/java ...).
>
>
>
>
> On Tue, Aug 6, 2013 at 7:29 PM, flmaven <jo...@hotmail.com> wrote:
>
>> Hello Ron,
>> Thanks for your reply.
>> Where I work there is no use of scripts for creating projects. There is a
>> base model that is used to create projects, but is not based on Maven, or
>> Ant, it was created by the company.
>> There is a "standard way", but this is not I am worried about.
>> Right now, I am just worried with having a project without Maven that
>> "would
>> do" the same as the Maven project "would do".
>> And this is what I am not understanding. I disabled the Maven nature of the
>> project, added all the jars that where necessary to the project, and it
>> won´t work.
>> That´s why I asked if there were other necessary steps to make besides
>> disable the Maven nature of the project and add the libs.
>> Is there other points that I should pay attention when I disable the Maven
>> nature of a project? What are they?
>> Thanks for your attention.
>>
>>
>> Ron Wheeler wrote
>>> You probably need to start by finding out how everyone at your
>>> organization builds projects.
>>> For example, do they use a set of Ant scripts?
>>>
>>> Maven gives you a standard way to do things but if your organization is
>>> not using Maven, it probably has a "standard" way that all of the
>>> projects are built.
>>> You may also need to restructure your source tree to match the
>>> organization's way of organizing a project.
>>>
>>> I can not think of any reason why it would be necessary to remove the
>>> pom.xml or tell Eclipse anything after you have removed the Maven nature.
>>>
>>> No one here can tell you how your organization builds its applications
>>> and that is what you need to find out.
>>>
>>> Ron
>>>
>>> On 05/08/2013 12:17 PM, flmaven wrote:
>>>> Hello,
>>>> English is not my native language; please excuse typing errors.
>>>> I need to "unmave" a project because in the place I work Maven is not
>>>> used.
>>>> The problem is that I downloaded a lot of source-code from a book and
>> all
>>>> it´s content are Maven Projects.
>>>> I found easy to make the projects work as Maven Projects... just import
>> a
>>>> Maven Project, configure my application server - I am using Jboss 7.0,
>>>> and
>>>> run them. I could easily configure this projects after testing it and
>>>> change
>>>> them to my needs.
>>>> But since we don´t use Maven here, I started trying to disable the Maven
>>>> nature of a project and I couldn´t get the project to work. I deleted
>> the
>>>> pom.xml file and added the libs that were necessary to the project
>>>> classpath
>>>> - after clicking in the Eclipse IDE to disable Maven nature.
>>>> Is there any other configuration needed? When I want to "unmaven"
>>>> project,
>>>> in addition to the libs, what should I pay attention?
>>>> Thanks for your attention.
>>>>
>>>>
>


-- 
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: "Unmaving" a project

Posted by Adrien Rivard <ad...@gmail.com>.
You should probably delete all  the eclipse files (.project .classpath,
.settings/* ) and recreate a new java project and eventually edit it to
match the maven project structure (src/main/java ...).




On Tue, Aug 6, 2013 at 7:29 PM, flmaven <jo...@hotmail.com> wrote:

> Hello Ron,
> Thanks for your reply.
> Where I work there is no use of scripts for creating projects. There is a
> base model that is used to create projects, but is not based on Maven, or
> Ant, it was created by the company.
> There is a "standard way", but this is not I am worried about.
> Right now, I am just worried with having a project without Maven that
> "would
> do" the same as the Maven project "would do".
> And this is what I am not understanding. I disabled the Maven nature of the
> project, added all the jars that where necessary to the project, and it
> won´t work.
> That´s why I asked if there were other necessary steps to make besides
> disable the Maven nature of the project and add the libs.
> Is there other points that I should pay attention when I disable the Maven
> nature of a project? What are they?
> Thanks for your attention.
>
>
> Ron Wheeler wrote
> > You probably need to start by finding out how everyone at your
> > organization builds projects.
> > For example, do they use a set of Ant scripts?
> >
> > Maven gives you a standard way to do things but if your organization is
> > not using Maven, it probably has a "standard" way that all of the
> > projects are built.
> > You may also need to restructure your source tree to match the
> > organization's way of organizing a project.
> >
> > I can not think of any reason why it would be necessary to remove the
> > pom.xml or tell Eclipse anything after you have removed the Maven nature.
> >
> > No one here can tell you how your organization builds its applications
> > and that is what you need to find out.
> >
> > Ron
> >
> > On 05/08/2013 12:17 PM, flmaven wrote:
> >> Hello,
> >> English is not my native language; please excuse typing errors.
> >> I need to "unmave" a project because in the place I work Maven is not
> >> used.
> >> The problem is that I downloaded a lot of source-code from a book and
> all
> >> it´s content are Maven Projects.
> >> I found easy to make the projects work as Maven Projects... just import
> a
> >> Maven Project, configure my application server - I am using Jboss 7.0,
> >> and
> >> run them. I could easily configure this projects after testing it and
> >> change
> >> them to my needs.
> >> But since we don´t use Maven here, I started trying to disable the Maven
> >> nature of a project and I couldn´t get the project to work. I deleted
> the
> >> pom.xml file and added the libs that were necessary to the project
> >> classpath
> >> - after clicking in the Eclipse IDE to disable Maven nature.
> >> Is there any other configuration needed? When I want to "unmaven"
> >> project,
> >> in addition to the libs, what should I pay attention?
> >> Thanks for your attention.
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >> http://maven.40175.n5.nabble.com/Unmaving-a-project-tp5766830.html
> >> Sent from the Maven - Users mailing list archive at Nabble.com.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail:
>
> > users-unsubscribe@.apache
>
> >> For additional commands, e-mail:
>
> > users-help@.apache
>
> >>
> >>
> >
> >
> > --
> > Ron Wheeler
> > President
> > Artifact Software Inc
> > email:
>
> > rwheeler@
>
> > skype: ronaldmwheeler
> > phone: 866-970-2435, ext 102
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
>
> > users-unsubscribe@.apache
>
> > For additional commands, e-mail:
>
> > users-help@.apache
>
>
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Unmaving-a-project-tp5766830p5766898.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Adrien Rivard

Re: "Unmaving" a project

Posted by flmaven <jo...@hotmail.com>.
Hello Ron,
Thanks for your reply.
Where I work there is no use of scripts for creating projects. There is a
base model that is used to create projects, but is not based on Maven, or
Ant, it was created by the company.
There is a "standard way", but this is not I am worried about. 
Right now, I am just worried with having a project without Maven that "would
do" the same as the Maven project "would do".
And this is what I am not understanding. I disabled the Maven nature of the
project, added all the jars that where necessary to the project, and it
won´t work.
That´s why I asked if there were other necessary steps to make besides
disable the Maven nature of the project and add the libs.
Is there other points that I should pay attention when I disable the Maven
nature of a project? What are they?
Thanks for your attention.


Ron Wheeler wrote
> You probably need to start by finding out how everyone at your 
> organization builds projects.
> For example, do they use a set of Ant scripts?
> 
> Maven gives you a standard way to do things but if your organization is 
> not using Maven, it probably has a "standard" way that all of the 
> projects are built.
> You may also need to restructure your source tree to match the 
> organization's way of organizing a project.
> 
> I can not think of any reason why it would be necessary to remove the 
> pom.xml or tell Eclipse anything after you have removed the Maven nature.
> 
> No one here can tell you how your organization builds its applications 
> and that is what you need to find out.
> 
> Ron
> 
> On 05/08/2013 12:17 PM, flmaven wrote:
>> Hello,
>> English is not my native language; please excuse typing errors.
>> I need to "unmave" a project because in the place I work Maven is not
>> used.
>> The problem is that I downloaded a lot of source-code from a book and all
>> it´s content are Maven Projects.
>> I found easy to make the projects work as Maven Projects... just import a
>> Maven Project, configure my application server - I am using Jboss 7.0,
>> and
>> run them. I could easily configure this projects after testing it and
>> change
>> them to my needs.
>> But since we don´t use Maven here, I started trying to disable the Maven
>> nature of a project and I couldn´t get the project to work. I deleted the
>> pom.xml file and added the libs that were necessary to the project
>> classpath
>> - after clicking in the Eclipse IDE to disable Maven nature.
>> Is there any other configuration needed? When I want to "unmaven"
>> project,
>> in addition to the libs, what should I pay attention?
>> Thanks for your attention.
>>
>>
>>
>> --
>> View this message in context:
>> http://maven.40175.n5.nabble.com/Unmaving-a-project-tp5766830.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

>> For additional commands, e-mail: 

> users-help@.apache

>>
>>
> 
> 
> -- 
> Ron Wheeler
> President
> Artifact Software Inc
> email: 

> rwheeler@

> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: http://maven.40175.n5.nabble.com/Unmaving-a-project-tp5766830p5766898.html
Sent from the Maven - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: "Unmaving" a project

Posted by Ron Wheeler <rw...@artifact-software.com>.
You probably need to start by finding out how everyone at your 
organization builds projects.
For example, do they use a set of Ant scripts?

Maven gives you a standard way to do things but if your organization is 
not using Maven, it probably has a "standard" way that all of the 
projects are built.
You may also need to restructure your source tree to match the 
organization's way of organizing a project.

I can not think of any reason why it would be necessary to remove the 
pom.xml or tell Eclipse anything after you have removed the Maven nature.

No one here can tell you how your organization builds its applications 
and that is what you need to find out.

Ron

On 05/08/2013 12:17 PM, flmaven wrote:
> Hello,
> English is not my native language; please excuse typing errors.
> I need to "unmave" a project because in the place I work Maven is not used.
> The problem is that I downloaded a lot of source-code from a book and all
> it´s content are Maven Projects.
> I found easy to make the projects work as Maven Projects... just import a
> Maven Project, configure my application server - I am using Jboss 7.0, and
> run them. I could easily configure this projects after testing it and change
> them to my needs.
> But since we don´t use Maven here, I started trying to disable the Maven
> nature of a project and I couldn´t get the project to work. I deleted the
> pom.xml file and added the libs that were necessary to the project classpath
> - after clicking in the Eclipse IDE to disable Maven nature.
> Is there any other configuration needed? When I want to "unmaven" project,
> in addition to the libs, what should I pay attention?
> Thanks for your attention.
>
>
>
> --
> View this message in context: http://maven.40175.n5.nabble.com/Unmaving-a-project-tp5766830.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org