Roadblocks and MovableTypeImporter, some progress made

[Chris Kruger-2]

Hello Pebble People,

I have made some progress with getting trunk going in Eclipse Indigo
with Apache Tomcat 7. The list below is the executive summary of what
I did to to get it running. I hope that it will help others or perhaps
some knowledgable others may be able work out why I experienced some
of my afore mentioned problems in the first place.

1. Create new workspace PEBBLE
2. Install Maven Eclipse plugin and WTP integration
2. File->Import->Maven->Checkout as Maven project from SCM
3. Enter svn, https://open.jira.com/svn/PEBBLE/trunk/ has svn uri
4. Select default pom.xml and next
5. resolve later for plugin connectors maven-antrun-plugin and maven-jaxb-plugin
6. Wait until materialised
7. Go to pom and the plugin maven-antrun-plugin snippet, right click
and choose quick fix. Choose to ignore.
8. Go to pom and the plugin maven-jaxb-plugin, right click and choose
to quick fix. Ignore.
9. Go to pom and find the pluginExecutionFilter for maven-jaxb-plugin,
in the action part, change the <ignore></ignore> to <execute />
10. Click on the project root in the Project Explorer, right click,
choose Maven submenu and Update Project Configuration.
11. Now got to Run menu, RunAs and choose Maven generate-source, this
does the jaxb generation part
12. In Project Explorer choose Pebble->Java Resources and right click.
Choose New->Source Folder. Choose Pebble Project, and Folder Name
target/generated-sources/xjc
13. This should fix all the java errors, once this new directory is compiled
14. Got into Pebble/src/main/resources and grab the pebble.tld, move
it to Pebble/src/main/webapp/WEB-INF
15. Select Pebble root, and the goto Debug button and Run On Server.
Configure Apache Tomcat 7.
16. Run it and you should see Pebble running.

Hope this helps somebody.


So two outstanding issues remain in my mind that that I feel would be
nice to solve before I start looking at MovableTypeImporter in more
depth. Accepting advice, suggestions etc here.

* The Jaxb generation is manual. I suspect this will only be solved by
upgrading to another jaxb generator that has a maven plugin, with
corresponding Eclipse Maven Lifecycle plugin. I suspect the jaxb maven
plugin used by pebble has effectively been deprecated.
* I don't really understand why the pebble.tld works if moved to
WEB-INF from META-INF. Do I understand correctly that is should work
from either? (As i have mentioned previously I'm not really a Java or
web guy so I am playing catchup here). Have I potentially got Eclipse
misconfigured?

Chris K.
chris.kruger@...

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user

[Weiqi Gao-2]

Eclipse is always misconfigured, no matter what you do.  Use IntelliJ IDEA instead.  I think Pebble committers are qualified to receive a free Open Source license of IntelliJ IDEA Ultimate license from JetBrains.

--
Weiqi Gao

On Feb 21, 2012, at 1:49 AM, Chris Kruger wrote:

> Hello Pebble People,
>
> I have made some progress with getting trunk going in Eclipse Indigo
> with Apache Tomcat 7. The list below is the executive summary of what
> I did to to get it running. I hope that it will help others or perhaps
> some knowledgable others may be able work out why I experienced some
> of my afore mentioned problems in the first place.
>
> 1. Create new workspace PEBBLE
> 2. Install Maven Eclipse plugin and WTP integration
> 2. File->Import->Maven->Checkout as Maven project from SCM
> 3. Enter svn, https://open.jira.com/svn/PEBBLE/trunk/ has svn uri
> 4. Select default pom.xml and next
> 5. resolve later for plugin connectors maven-antrun-plugin and maven-jaxb-plugin
> 6. Wait until materialised
> 7. Go to pom and the plugin maven-antrun-plugin snippet, right click
> and choose quick fix. Choose to ignore.
> 8. Go to pom and the plugin maven-jaxb-plugin, right click and choose
> to quick fix. Ignore.
> 9. Go to pom and find the pluginExecutionFilter for maven-jaxb-plugin,
> in the action part, change the <ignore></ignore> to <execute />
> 10. Click on the project root in the Project Explorer, right click,
> choose Maven submenu and Update Project Configuration.
> 11. Now got to Run menu, RunAs and choose Maven generate-source, this
> does the jaxb generation part
> 12. In Project Explorer choose Pebble->Java Resources and right click.
> Choose New->Source Folder. Choose Pebble Project, and Folder Name
> target/generated-sources/xjc
> 13. This should fix all the java errors, once this new directory is compiled
> 14. Got into Pebble/src/main/resources and grab the pebble.tld, move
> it to Pebble/src/main/webapp/WEB-INF
> 15. Select Pebble root, and the goto Debug button and Run On Server.
> Configure Apache Tomcat 7.
> 16. Run it and you should see Pebble running.
>
> Hope this helps somebody.
>
>
> So two outstanding issues remain in my mind that that I feel would be
> nice to solve before I start looking at MovableTypeImporter in more
> depth. Accepting advice, suggestions etc here.
>
> * The Jaxb generation is manual. I suspect this will only be solved by
> upgrading to another jaxb generator that has a maven plugin, with
> corresponding Eclipse Maven Lifecycle plugin. I suspect the jaxb maven
> plugin used by pebble has effectively been deprecated.
> * I don't really understand why the pebble.tld works if moved to
> WEB-INF from META-INF. Do I understand correctly that is should work
> from either? (As i have mentioned previously I'm not really a Java or
> web guy so I am playing catchup here). Have I potentially got Eclipse
> misconfigured?
>
> Chris K.
> chris.kruger@...
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Pebble-user mailing list
> Pebble-user@...
> https://lists.sourceforge.net/lists/listinfo/pebble-user
>

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user

[James Roper-6]

Hi Chris,

Sorry for not replying, I've been pretty busy of late.  A few notes:

* I recommend using the 2.6 branch of Pebble... trunk is in the middle
of some major refactorings, and there is one known issue (category
index is broken).  It does work (I'm running trunk on my server), but
you may find it easier to use the 2.6 branch, particularly for the
importers, because I've been slowly getting rid of all Pebbles
singletons, and replacing it all with dependency injection... the
importers need to be updated to support this properly.
* Generating the JAXB classes is a relic of when Pebble used JAXB 1.x.
 My intention is to get rid of this and replace it with a JAXB
annotated class, so no generation is required, but I just haven't got
around to it.
* I use IntelliJ IDEA, and I've found it has no problems just opening
the project as a maven project after running mvn generate-sources.
Weiqi is right, I have an open source license for IDEA for Pebble
development, but I'm not sure what the rules are with giving this out.
* I've never been an expert on JSP libraries, and I don't understand
either the intricacies of where TLD files should live.  I think it
should work from either.  It's possible that Eclipse isn't copying
resources to the right place, or isn't setting up classpaths properly.

Cheers,

James

On 21 February 2012 13:48, Weiqi Gao <weiqigao@...> wrote:

> Eclipse is always misconfigured, no matter what you do.  Use IntelliJ IDEA instead.  I think Pebble committers are qualified to receive a free Open Source license of IntelliJ IDEA Ultimate license from JetBrains.
>
> --
> Weiqi Gao
>
> On Feb 21, 2012, at 1:49 AM, Chris Kruger wrote:
>
>> Hello Pebble People,
>>
>> I have made some progress with getting trunk going in Eclipse Indigo
>> with Apache Tomcat 7. The list below is the executive summary of what
>> I did to to get it running. I hope that it will help others or perhaps
>> some knowledgable others may be able work out why I experienced some
>> of my afore mentioned problems in the first place.
>>
>> 1. Create new workspace PEBBLE
>> 2. Install Maven Eclipse plugin and WTP integration
>> 2. File->Import->Maven->Checkout as Maven project from SCM
>> 3. Enter svn, https://open.jira.com/svn/PEBBLE/trunk/ has svn uri
>> 4. Select default pom.xml and next
>> 5. resolve later for plugin connectors maven-antrun-plugin and maven-jaxb-plugin
>> 6. Wait until materialised
>> 7. Go to pom and the plugin maven-antrun-plugin snippet, right click
>> and choose quick fix. Choose to ignore.
>> 8. Go to pom and the plugin maven-jaxb-plugin, right click and choose
>> to quick fix. Ignore.
>> 9. Go to pom and find the pluginExecutionFilter for maven-jaxb-plugin,
>> in the action part, change the <ignore></ignore> to <execute />
>> 10. Click on the project root in the Project Explorer, right click,
>> choose Maven submenu and Update Project Configuration.
>> 11. Now got to Run menu, RunAs and choose Maven generate-source, this
>> does the jaxb generation part
>> 12. In Project Explorer choose Pebble->Java Resources and right click.
>> Choose New->Source Folder. Choose Pebble Project, and Folder Name
>> target/generated-sources/xjc
>> 13. This should fix all the java errors, once this new directory is compiled
>> 14. Got into Pebble/src/main/resources and grab the pebble.tld, move
>> it to Pebble/src/main/webapp/WEB-INF
>> 15. Select Pebble root, and the goto Debug button and Run On Server.
>> Configure Apache Tomcat 7.
>> 16. Run it and you should see Pebble running.
>>
>> Hope this helps somebody.
>>
>>
>> So two outstanding issues remain in my mind that that I feel would be
>> nice to solve before I start looking at MovableTypeImporter in more
>> depth. Accepting advice, suggestions etc here.
>>
>> * The Jaxb generation is manual. I suspect this will only be solved by
>> upgrading to another jaxb generator that has a maven plugin, with
>> corresponding Eclipse Maven Lifecycle plugin. I suspect the jaxb maven
>> plugin used by pebble has effectively been deprecated.
>> * I don't really understand why the pebble.tld works if moved to
>> WEB-INF from META-INF. Do I understand correctly that is should work
>> from either? (As i have mentioned previously I'm not really a Java or
>> web guy so I am playing catchup here). Have I potentially got Eclipse
>> misconfigured?
>>
>> Chris K.
>> chris.kruger@...
>>
>> ------------------------------------------------------------------------------
>> Keep Your Developer Skills Current with LearnDevNow!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-d2d
>> _______________________________________________
>> Pebble-user mailing list
>> Pebble-user@...
>> https://lists.sourceforge.net/lists/listinfo/pebble-user
>>
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Pebble-user mailing list
> Pebble-user@...
> https://lists.sourceforge.net/lists/listinfo/pebble-user

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user

[geezenslaw]

+1


On Tue, 2012-02-21 at 06:48 -0600, Weiqi Gao wrote:

> Eclipse is always misconfigured, no matter what you do.  Use IntelliJ IDEA instead.  I think Pebble committers are qualified to receive a free Open Source license of IntelliJ IDEA Ultimate license from JetBrains.
>
> --
> Weiqi Gao
>
> On Feb 21, 2012, at 1:49 AM, Chris Kruger wrote:
>
> > Hello Pebble People,
> >
> > I have made some progress with getting trunk going in Eclipse Indigo
> > with Apache Tomcat 7. The list below is the executive summary of what
> > I did to to get it running. I hope that it will help others or perhaps
> > some knowledgable others may be able work out why I experienced some
> > of my afore mentioned problems in the first place.
> >
> > 1. Create new workspace PEBBLE
> > 2. Install Maven Eclipse plugin and WTP integration
> > 2. File->Import->Maven->Checkout as Maven project from SCM
> > 3. Enter svn, https://open.jira.com/svn/PEBBLE/trunk/ has svn uri
> > 4. Select default pom.xml and next
> > 5. resolve later for plugin connectors maven-antrun-plugin and maven-jaxb-plugin
> > 6. Wait until materialised
> > 7. Go to pom and the plugin maven-antrun-plugin snippet, right click
> > and choose quick fix. Choose to ignore.
> > 8. Go to pom and the plugin maven-jaxb-plugin, right click and choose
> > to quick fix. Ignore.
> > 9. Go to pom and find the pluginExecutionFilter for maven-jaxb-plugin,
> > in the action part, change the <ignore></ignore> to <execute />
> > 10. Click on the project root in the Project Explorer, right click,
> > choose Maven submenu and Update Project Configuration.
> > 11. Now got to Run menu, RunAs and choose Maven generate-source, this
> > does the jaxb generation part
> > 12. In Project Explorer choose Pebble->Java Resources and right click.
> > Choose New->Source Folder. Choose Pebble Project, and Folder Name
> > target/generated-sources/xjc
> > 13. This should fix all the java errors, once this new directory is compiled
> > 14. Got into Pebble/src/main/resources and grab the pebble.tld, move
> > it to Pebble/src/main/webapp/WEB-INF
> > 15. Select Pebble root, and the goto Debug button and Run On Server.
> > Configure Apache Tomcat 7.
> > 16. Run it and you should see Pebble running.
> >
> > Hope this helps somebody.
> >
> >
> > So two outstanding issues remain in my mind that that I feel would be
> > nice to solve before I start looking at MovableTypeImporter in more
> > depth. Accepting advice, suggestions etc here.
> >
> > * The Jaxb generation is manual. I suspect this will only be solved by
> > upgrading to another jaxb generator that has a maven plugin, with
> > corresponding Eclipse Maven Lifecycle plugin. I suspect the jaxb maven
> > plugin used by pebble has effectively been deprecated.
> > * I don't really understand why the pebble.tld works if moved to
> > WEB-INF from META-INF. Do I understand correctly that is should work
> > from either? (As i have mentioned previously I'm not really a Java or
> > web guy so I am playing catchup here). Have I potentially got Eclipse
> > misconfigured?
> >
> > Chris K.
> > chris.kruger@...
> >
> > ------------------------------------------------------------------------------
> > Keep Your Developer Skills Current with LearnDevNow!
> > The most comprehensive online learning library for Microsoft developers
> > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> > Metro Style Apps, more. Free future releases when you subscribe now!
> > http://p.sf.net/sfu/learndevnow-d2d
> > _______________________________________________
> > Pebble-user mailing list
> > Pebble-user@...
> > https://lists.sourceforge.net/lists/listinfo/pebble-user
> >
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Pebble-user mailing list
> Pebble-user@...
> https://lists.sourceforge.net/lists/listinfo/pebble-user

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user

[Chris Kruger-2]

On Tue, Feb 21, 2012 at 9:38 PM, James Roper <james@...> wrote:

> Hi Chris,
>
> Sorry for not replying, I've been pretty busy of late.  A few notes:
>
> * I recommend using the 2.6 branch of Pebble... trunk is in the middle
> of some major refactorings, and there is one known issue (category
> index is broken).  It does work (I'm running trunk on my server), but
> you may find it easier to use the 2.6 branch, particularly for the
> importers, because I've been slowly getting rid of all Pebbles
> singletons, and replacing it all with dependency injection... the
> importers need to be updated to support this properly.

Ok understood. I'll use 2.6

> * Generating the JAXB classes is a relic of when Pebble used JAXB 1.x.
>  My intention is to get rid of this and replace it with a JAXB
> annotated class, so no generation is required, but I just haven't got
> around to it.

np.

> * I use IntelliJ IDEA, and I've found it has no problems just opening
> the project as a maven project after running mvn generate-sources.
> Weiqi is right, I have an open source license for IDEA for Pebble
> development, but I'm not sure what the rules are with giving this out.

I don't think I qualify. At least, not yet. I'm not a committer on any
Java projects.

> * I've never been an expert on JSP libraries, and I don't understand
> either the intricacies of where TLD files should live.  I think it
> should work from either.  It's possible that Eclipse isn't copying
> resources to the right place, or isn't setting up classpaths properly.

After some further investigation I think you're right. The resources
are somehow being skipped and are no accessible to Tomcat when I hit
debug. I'll look into it more.

Is data format compatible between 2.6 and trunk?

Chris K.
chris.kruger@...

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user

[Chris Kruger-2]

> * I don't really understand why the pebble.tld works if moved to
> WEB-INF from META-INF. Do I understand correctly that is should work
> from either? (As i have mentioned previously I'm not really a Java or
> web guy so I am playing catchup here). Have I potentially got Eclipse
> misconfigured?

Ok so I have an update on why I was experiencing this problem. The
following tomcat-users mailing list archive thread explains.

http://mail-archives.apache.org/mod_mbox/tomcat-users/201102.mbox/%3c9316C6C55336DA4BB9CAD5754DF88C5A027CA96D8F@...%3e

executive summary. On Tomcat 7

"Looks like the TldConfig class changed significantly between these
versions such that
now TLDs that are under WEB-INF/classes (e.g.
WEB-INF/classes/META-INF) are no longer scanned/processed."

Tomcat 6 works fine without moving pebble.tld.

I point this out because of the mention of spec change and thought it
might crop up as a problem for others later.

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user